• 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:05:21 -0400 (EDT)
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <42531273.7080102@l...>

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

You've doubled the reliability, security, and server-state load,
but it is RESTian.  For many applications that won't be enough.
	/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...>

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