• To: Michael Champion <michaelc.champion@g...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Joe Gregorio <joe.gregorio@g...>
• Date: Wed, 30 Mar 2005 12:32:11 -0500
• Cc: xml-dev@l...
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=GDdbFrIfl+XzETAVmtxIBJ5rBEviVZ4NQSm1C6lQ5luTnPFvW4CSXj4IjcEZPpCtH1rRdz0uaPHfKMRu4om93EGPhSjuHIo4p/R3+r6Hh0WASCmnxTD/Iqh/YNsemjUYG5ycNU+4f1h5HP/Wk7XxC/d54p8zIMRtLVBsRrz2Lyk=
• In-reply-to: <e3a5cb2c05033008513cd5486c@m...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D57@h...> <e3a5cb2c05033008513cd5486c@m...>
• Reply-to: Joe Gregorio <joe.gregorio@g...>

On Wed, 30 Mar 2005 11:51:18 -0500, Michael Champion
<michaelc.champion@g...> wrote:
> Mu.  REST is a protocol, SOAP is a message format.  <duck>

REST is an architectural style, SOAP is a message format.

> Basically REST offers a discipline for making lemonade out of these
> lemons, whereas WS-* offers a wide range of genetically modified sweet
> lemons that you can supposedly eat right off the tree.

Oooh, I like that.

   -joe

-- 
Joe Gregorio        http://bitworking.org

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Michael Champion <michaelc.champion@g...>

• References:
  • What Does SOAP/WS Do that A REST System Can't?
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Michael Champion <michaelc.champion@g...>

• Prev by Date: RE: XQuery Adoption Survey Results
• Next by Date: RE: What Does SOAP/WS Do that A REST System Can't?
• 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