• To: xml-dev <xml-dev@l...>
• Subject: Re: Exposing resources/services vs hiding implementation details
• From: Michael Champion <michaelc.champion@g...>
• Date: Tue, 5 Apr 2005 20:06:59 -0400
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=WDArd//N4dFqMMrTzki0m4peClSK+9KEvUEe+2J7/n5L9+S8OCpWSMPcbylVjBxQL9C46yaoJLsw0mH06BSzdw1cvZmyfWzUsclZNXzC9Qrg5kQg5vbu7zZKy0kFj51BVkQkAwTPGnLyUla8nHTpTLQsj2R6IXwblTRx3DfI9DA=
• In-reply-to: <42531B33.5000503@p...>
• References: <200504051139.j35BdXDR050954@s...> <42528FB5.7040300@p...> <e3a5cb2c0504050804887b795@m...> <4252B1D7.8090707@t...> <1112725099.7722.400.camel@borgia> <4252EE77.1080604@d...> <4252F528.5050503@t...> <e3a5cb2c050405144329d3ed74@m...> <42531B33.5000503@p...>
• Reply-to: Michael Champion <michaelc.champion@g...>

On Apr 5, 2005 7:11 PM, Bill de hÓra <bill.dehora@p...> 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>.

• Follow-Ups:
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Bill de hÓra <bill.dehora@p...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Robert Koberg <rob@k...>

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Marc de Graauw" <marc@m...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Bill de hÓra <bill.dehora@p...>
  • Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Jan Algermissen <jalgermissen@t...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Rich Salz <rsalz@d...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Jan Algermissen <jalgermissen@t...>
  • Re: Exposing resources/services vs hiding implementation details
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Bill de hÓra <bill.dehora@p...>

• Prev by Date: Re: Exposing resources/services vs hiding implementation details
• Next by Date: Re: Exposing resources/services vs hiding implementation details
• Previous by thread: Re: Exposing resources/services vs hiding implementationdetails
• Next by thread: Re: Exposing resources/services vs hiding implementationdetails
• Index(es):
  • Date
  • Thread