• To: xml-dev@l...
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Michael Champion <michaelc.champion@g...>
• Date: Wed, 30 Mar 2005 15:41:19 -0500
• 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=doGfuFuO5a3Lz6pMNAFnajsvULLbgA/AnsoTdohCfhUHgWReSrVuHgHkb0UDxq+oK4ineHCYCOIjHqcLojjOMc6vMQF40ooMOdX3HTdRuREbufzhswHpcDYiroIGw5mRzuOU6snBfI3Gljqa+/vWCkMgjY5NYMmt14jxZRGnZNc=
• In-reply-to: <830178CE7378FC40BC6F1DDADCFDD1D104782233@R...>
• References: <830178CE7378FC40BC6F1DDADCFDD1D104782233@R...>
• Reply-to: Michael Champion <michaelc.champion@g...>

On Wed, 30 Mar 2005 10:01:42 -0800, Dare Obasanjo <dareo@m...> wrote:

> >   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. 

Fair enough.  I was talking about the permathread abstract discussions
of architectural styles, service architectures, etc., i.e. "high REST"
in Nelson Minar's terminology.  I agree that the question of "low
REST" vs WS-* does come down to rich vs reach.

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: "W. E. Perry" <wperry@f...>

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: XQuery Adoption Survey Results
• Previous by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread