W3C home > Mailing lists > Public > www-tag@w3.org > May 2002

RE: TAG document: SOAP HTTP GET binding available

From: Sam Ruby <rubys@us.ibm.com>
Date: Tue, 7 May 2002 18:48:42 -0400
To: <www-tag@w3.org>
Message-ID: <OF4D4E2A46.9EF0ECDA-ON85256BB2.007C2DF6-85256BB2.007D4F23@raleigh.ibm.com>
David Orchard wrote:
>
> A sample usage scenario that I see is that a user creates a web service and
> marks it as "safe".  A tool then automatically generates a SOAP HTTP POST
> binding and a GET binding in the WSDL.  Their runtime software could be
> configured to automatically map the GET invokes into a POST invoke, perhaps
> based upon the "safe" attribute in WSDL.  The user only had to create one
> implementation (the POST) and the user did not have to define the
> transcoding algorithm.

What you are describing is precisely what .NET does today modulo a few
important details.

*  In ASP.NET one provides only one implementation of a service (in the
   form of a .ASMX), and in there one can optionally select via attributes
   which bindings are to be automatically provided by the runtime.  One can
   question .NET's defaults (it currently automatically provides a GET
   binding if the parameters are simple enough), but these are merely
   defaults.

*  The HTTP GET bindings provided are the ones specified in the WSDL
   specification.  I can only presume that you have some issue with these
   as you are now providing a new specification.

Glue's implementation is similar... though to date I am not aware of any
way to override the default nor any way to use these bindings from the
client.

We could discuss what is reasonable policies for defaults, and what "knobs"
a soap implementation should provide, but I would prefer that we start such
discussions based on what is already provided in the standard and
implemented instead of providing yet another binding.

- Sam Ruby
Received on Tuesday, 7 May 2002 18:50:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:51 UTC