• To: Leigh Dodds <leigh@l...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Rich Salz <rsalz@d...>
• Date: Tue, 5 Apr 2005 19:24:22 -0400 (EDT)
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <42531AA4.70605@l...>

> > You've doubled the reliability, security, and server-state load,
> > but it is RESTian.  For many applications that won't be enough.
>
> Where do you get the factor of two from?

Twice the number of HTTP messages, nothing more simple then that.
As for server-state, the server now has to maintain state behind
the GET'able URL, make sure that it's the same client coming back
or otherwise deal with authorization decisions, etc.
	/r$

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

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Leigh Dodds <leigh@l...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Bob Foster <bob@o...>

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

• Prev by Date: Re: Exposing resources/services vs hiding implementationdetails
• Next by Date: Re: Exposing resources/services vs hiding implementationdetails
• 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