• To: Rich Salz <rsalz@d...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Rick Marshall <rjm@z...>
• Date: Thu, 14 Apr 2005 15:41:31 +1000
• Cc: Joe Gregorio <joe.gregorio@g...>, "xml-dev@l..." <xml-dev@l...>
• In-reply-to: <Pine.LNX.4.44L0.0504132307440.16250-100000@s...>
• Organization: Zenucom Pty Ltd
• References: <Pine.LNX.4.44L0.0504132307440.16250-100000@s...>
• User-agent: Mozilla Thunderbird 0.6 (X11/20040502)

Rich Salz wrote:

>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$
>
>  
>
http 1.1 has persistent connections for long transactions. won't that do 
the job?

in fact soap relies on it....

rick

begin:vcard
fn:Rick  Marshall
n:Marshall;Rick 
email;internet:rjm@z...
tel;cell:+61 411 287 530
x-mozilla-html:TRUE
version:2.1
end:vcard

• 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: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: [ANN] XML Enhancements for Java 1.0
• 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