[
Lists Home |
Date Index |
Thread Index
]
On Tue, 2005-04-05 at 20:06 -0400, Michael Champion wrote:
> On Apr 5, 2005 7:11 PM, Bill de hÓra <bill.dehora@propylon.com> wrote:
> > > *if* your users do far more read operations than create/update/delete
> > > operations, and there is a high probability that a document that is
> > > retrieved once will be requested again soon.. Very true on the Web.
> > > Not true for data enty applications. Nightmarishly difficult in the
> > > distributed read/write case.
> >
> > Don't understand the last bit - nightmarishly difficult how?
>
> I was thinking of the quote attributed to Phil Karlton
> (http://lists.xml.org/archives/xml-dev/200001/msg00170.html) "There
> are only two hard problems in computer science, cache invalidation and
> naming things."
>
> Hmm, REST assumes that both of them have been solved <duck>.
Oh brother. So does:
relational DBMS
The Internet
The Web
[snip 1000 other examples]
and *drum roll please*
Wizard Web Services (i.e. the sort you advocate)
It's a miracle we get *anything* accomplished, despite hard problems,
eh?
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
Writing and Reading XML with XIST - http://www.xml.com/pub/a/2005/03/16/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
State of the art in XML modeling - http://www.ibm.com/developerworks/xml/library/x-think30.html
|
