[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Evaluating RPC versus REST

• To: xml-dev <xml-dev@l...>
• Subject: RE: Evaluating RPC versus REST
• From: Mike Champion <mc@x...>
• Date: Tue, 26 Feb 2002 11:04:05 -0500
• In-reply-to: <2C61CCE8A870D211A523080009B94E4306FEE92D@HQ5>

2/26/2002 10:27:42 AM, "Bullard, Claude L (Len)" <clbullar@i...> wrote:


>What are the efficiencies gained by tight coupling of 
>enterprise (intra and extra) processes vs the loose 
>couplings based on standard document types?  

We won't know for a long time.  Recalling the Wired
article I mentioned in a precious post, the people standardizing
the Whitworth screw thread in 1824 couldn't know that their
decision would jeopardize the Empire in 1942.  Would a 
"loosely coupled" truck design that didn't require 
people in Detroit to have detailed knowledge of the
screw thread machines in Manchester have worked better?
Maybe, but then folks out in the desert might be throwing
away whole engines for the lack of a bolt ....

I just want to make sure that a decision to standardize on
the RPC paradigm today doesn't lose us a war with the
aliens in 2150, as all those threads waiting for a
response to an RPC invocation of a web service light-minutes
away lock up the command and control systems <grin>.

• References:
  • RE: Evaluating RPC versus REST
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: RE: MS thinks HTTP Needs Replacing???
• Next by Date: RE: MS thinks HTTP Needs Replacing???
• Previous by thread: RE: Evaluating RPC versus REST
• Next by thread: RE: Evaluating RPC versus REST
• Index(es):
  • Date
  • Thread