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

RE: SOAP and the Web

• To: "Mike Deem" <mikedeem@m...>,"Bullard, Claude L (Len)" <clbullar@i...>
• Subject: RE: SOAP and the Web
• From: Rex Brooks <rexb@s...>
• Date: Wed, 1 May 2002 13:37:39 -0700
• Cc: "xml-dev" <xml-dev@l...>
• In-reply-to: <A84507FC48EA7B4B86323F4E82483F7E024BA72A@r...>
• References: <A84507FC48EA7B4B86323F4E82483F7E024BA72A@r...>

Could you suggest ways in which REST and SOAP could merge? I am well 
aware of the support for SOAP, and its unambiguous xml package 
content feature.  The fact that it anticipates asynchronous 
functionality is IMHO the single most necessary feature for what is 
called web services. Since REST is an architecture and SOAP is 
package wrapper method, are there reasons why SOAP could not fit 
inside REST?

Ciao,
Rex

At 12:15 PM -0700 5/1/02, Mike Deem wrote:
>After re-reading my response, I think I can posit a high level summery.
>
>To build robust distributed systems in a decentralized way, you MUST
>have layers above the low level primitives offered by a network level
>architecture. As things currently stand, SOAP and REST are different low
>level architectures. Perhaps they can and should merge, that is an
>argument for a different thread.
>
>The key difference is that a community is actively moving forward with
>defining, implementing, packaging (in tools and application platforms),
>and testing for interoperability these layers built on SOAP. To my
>knowledge, no such effort is underway for REST. That is the payoff of
>SOAP.
>
>   == Mike ==
>
<snip>
-- 

• Follow-Ups:
  • Re: SOAP and the Web
    • From: Paul Prescod <paul@p...>

• References:
  • RE: SOAP and the Web
    • From: "Mike Deem" <mikedeem@m...>

• Prev by Date: Re: SOAP and the Web
• Next by Date: Re: Re: I can XInclude where I bloody want to
• Previous by thread: RE: SOAP and the Web
• Next by thread: Re: SOAP and the Web
• Index(es):
  • Date
  • Thread