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

• To: Michael Champion <michaelc.champion@...>
• Subject: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
• From: Jan Algermissen <jalgermissen@...>
• Date: Wed, 30 Mar 2005 20:27:57 +0200
• Cc: xml-dev@...
• In-reply-to: <e3a5cb2c05033009505aea47da@...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D57@...> <e3a5cb2c05033008513cd5486c@...> <3f1451f505033009326bbdc1ba@...> <e3a5cb2c05033009505aea47da@...>
• Reply-to: algermissen@...
• User-agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)

Michael Champion wrote:

>On Wed, 30 Mar 2005 12:32:11 -0500, Joe Gregorio <joe.gregorio@...> wrote:
>
>  
>
>>>Mu.  REST is a protocol, SOAP is a message format.  <duck>
>>>      
>>>
>>REST is an architectural style, SOAP is a message format.
>>    
>>
>
>You're right of course.  SOA is also an architectural style.
>  
>
Does anyone know of a sound definition of the 'SOA architectural style'? 
It would help a lot if one could compare the list of architectural 
constraints that define the REST style with the set of architectural 
constraints that define the SOA style.

Based on the architectural constraints it would be a lot easier to 
discuss the properties they induce to SOA style systems.

Jan

-- 
Jan Algermissen
Consultant & Programmer
http://jalgermissen.com

• Prev by Date: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
• Previous by thread: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread