• To: Joe Gregorio <joe.gregorio@g...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Rich Salz <rsalz@d...>
• Date: Wed, 13 Apr 2005 23:11:39 -0400 (EDT)
• Cc: "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <3f1451f505041320047877484b@m...>

Sorry if conflating HTTP and HTTP/REST bothered you.  I guess I don't
understand the differences all that well.

I thought I understood, and answered your question.

	Q. HTTP is extensible, why can't you build what you need?
	A. Because I need shared state, and because every
	   client operation ends up being a POST.  The first
	   seems impossible, and the second means the framework
	   benefits are nil.

Or am I still missing the point?

(I hate it when the limitation of the medium mean that two ostensibly
reasonable people end up getting all ticked off at each other.
Perhaps we should talk on the phone?)

	/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: Joe Gregorio <joe.gregorio@g...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Rick Marshall <rjm@z...>

• References:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Joe Gregorio <joe.gregorio@g...>

• Prev by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• 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