[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What Does SOAP/WS Do that A REST System Can't?

• To: Rich Salz <rsalz@d...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Bob Foster <bob@o...>
• Date: Tue, 05 Apr 2005 18:31:48 -0700
• Cc: Leigh Dodds <leigh@l...>,"xml-dev@l..." <xml-dev@l...>
• In-reply-to: <Pine.LNX.4.44L0.0504051921250.8517-100000@s...>
• References: <Pine.LNX.4.44L0.0504051921250.8517-100000@s...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

Rich Salz wrote:
>>>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.

Not more complex, either. If you doubled the number of connections, that 
would double the load. Messages, I don't think so. What you have done is 
doubled the latency.

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

Or encode the client identification in the URL.

Bob Foster

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

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