• To: Rich Salz <rsalz@d...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Dave Pawson <davep@d...>
• Date: Thu, 14 Apr 2005 19:06:23 +0100
• Cc: Joe Gregorio <joe.gregorio@g...>, "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <Pine.LNX.4.44L0.0504132234140.16250-100000@s...>
• References: <Pine.LNX.4.44L0.0504132234140.16250-100000@s...>
• Reply-to: davep@d...

On Wed, 2005-04-13 at 22:54 -0400, Rich Salz wrote:

> 
> I believe the very statelessness of HTTP and REST makes it
> impossible.  (Yeah, I know, it's not really without state, it's just
> that all the state is in the representations sent back and forth.
> Not good enough -- you need *shared state* that doesn't get
> communicated.  Go see the SSL/TLS or WS-SecureConversation specs.)

Can a comparison be made between the shift to  a REST based approach
and the shift from a procedural to a functional language? Getting
used to working without (modifiable) variables wasn't easy for me.
Same way, hacking web pages together without state is 'different'.

Is the mindset change comparable?

regards DaveP

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

• Prev by Date: RE: Is the XML Schema Test Collection still alive
• Next by Date: XML-enabled databases, XQuery APIs
• Previous by thread: Stateless security
• Next by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread