• To: Rich Salz <rsalz@d...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Leigh Dodds <leigh@l...>
• Date: Wed, 06 Apr 2005 00:09:24 +0100
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <Pine.LNX.4.44L0.0504051904060.5404-100000@s...>
• References: <Pine.LNX.4.44L0.0504051904060.5404-100000@s...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Rich Salz wrote:
>>POST to a URL.
>>Receive 302 See Other with a Location header.
>>Perform a GET on the URL in the Location header to see the results.
> 
> Cute.

Its a fairly standard pattern. I've got it deployed in a fairly
active human-oriented web application at the moment and its
working just fine.

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

L.

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

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

• Prev by Date: Re: XML 2005 Call for Participation Now Open - Deadline May 13
• 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