W3C home > Mailing lists > Public > www-ws-arch@w3.org > December 2002

Re: WSD Requirements: add a requirement about safe and idempotent characteristics

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Thu, 05 Dec 2002 11:58:38 +0100
Message-ID: <3DEF315E.9000204@crf.canon.fr>
To: Assaf Arkin <arkin@intalio.com>
CC: Mark Baker <distobj@acm.org>, www-ws-arch@w3.org


I'd like to point out that SOAP 1.2 also supports HTTP GET, for 
exactly the same reasons as HTTP, so as of now there should be no 
difference in the way we use SOAP from HTTP (at least at a 
certain level ;)).


Assaf Arkin wrote:
> The WEB offers me two ways to submit such a request: GET and POST. If my
> market position is not too complex I could fit it in a single URL and submit
> a GET request. This is what Dave is highlighting as a problem and I
> definitely agree.
> I would argue that if I use SOAP as the request mechanism, since the input
> message can be of arbitrary size I would always use POST. But even if I use
> HTTP bindings (without SOAP encoding) I should either always use GET or
> always use POST and not mix access methods for that same operation.
> This is one case where you should always use POST, in particular if you are
> doing SOAP, and this is one case where the operation you are performing is
> idempotent even though it happens using HTTP POST. So an 'idempotent'
> attribute definitely does not mandate which HTTP operation you would do but
> defines that characteristic of the WSDL operation you are doing.
Received on Thursday, 5 December 2002 05:58:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:01 UTC