OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] What Does SOAP/WS Do that A REST System Can't?

[ Lists Home | Date Index | Thread Index ]
  • To: "Michael Champion" <michaelc.champion@gmail.com>,<xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
  • From: "Dare Obasanjo" <dareo@microsoft.com>
  • Date: Wed, 30 Mar 2005 10:01:42 -0800
  • Thread-index: AcU1UXae/D94ACKES7GUFVVAoCT6jwAAIJIA
  • Thread-topic: [xml-dev] What Does SOAP/WS Do that A REST System Can't?

> -----Original Message-----
> From: Michael Champion [mailto:michaelc.champion@gmail.com] 
> Sent: Wednesday, March 30, 2005 9:50 AM
> To: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
>   I *think* the whole SOAP vs REST permathread  comes down to 
> Resource-orientation vs Service-orientation ... 

I completely disagree with that. SOAP vs. REST is rich vs. reach. The
question is do I want a richer, more fully featured web service
interface(SOAP + WSDL) that is supported on a handful of tools and
platforms or a less featureful web service interface(REST/POX) that is
supported in a majority of tools and platforms? 

If every platform had excellent support for SOAP+WSDL including the
monster that is XSD, then we wouldn't be having this debate. This is the
same way railing against Javascript-based websites became passe once
Firefox cloned a bunch of the IE-specific APIs and Google started using
them to build their newer websites. 

A man who can smile when everything has gone wrong has probably thought
of who he can blame it on.  

This posting is provided "AS IS" with no warranties, and confers no


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS