- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Thu, 27 Jun 2002 10:44:13 +0200
- To: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
- CC: www-ws-desc@w3.org
Regarding issue 6a, I am wondering whether the situation has not changed with the introduction of SOAP's support for HTTP GET. SOAP safe and idempotent requests are now supposed to be transported over HTTP GET. In such case, no SOAP envelope/infoset will be contained in HTTP's body. The necessary parameters are supposed to be included in the URI for the request, but the format for the URI is unspecified (by SOAP). Is this another argument for the feature you proposed earlier, http:urlXML, but this time also applicable to the SOAP binding? Jean-Jacques. Jeffrey Schlimmer wrote: > 6a. Define encoding of complex types in a request URL > 41. Define encoding of attributes in a request URL > > Recommend no change to WSDL spec. Not all bindings can encode all > messages. Leave HTTP request URLs segmented, flat, and (somewhat) human > readable. Discussion at [3, 4, 5]. > > > [3] http://lists.w3.org/Archives/Public/www-ws-desc/2002Apr/0183.html > [4] http://lists.w3.org/Archives/Public/www-ws-desc/2002May/0099.html > [5] http://lists.w3.org/Archives/Public/www-ws-desc/2002May/0146.html
Received on Thursday, 27 June 2002 04:44:51 UTC