• To: Leigh Dodds <leigh@l...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Rich Salz <rsalz@d...>
• Date: Wed, 06 Apr 2005 10:38:40 -0400
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <4253AFAF.7050804@l...>
• References: <Pine.LNX.4.44L0.0504051921250.8517-100000@s...> <4253AFAF.7050804@l...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421

> So I accept that yes there are 2 messages, but there's a lot of 
> variables to consider and options available. I'm not sure I see those
> same options with a "POST to controller; return response" approach.

I'll buy that.  The WS approach is to make asynchrony explicit in the 
message exchange.  Modulo server state and security issues, it's 
something you get "for free" with HTTP.

	/r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html

• References:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Rich Salz <rsalz@d...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Leigh Dodds <leigh@l...>

• Prev by Date: JavaScript & The Document Object Model (DOM) & XML
• Next by Date: Monty Python REST joke
• 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