Re: 1.2 Http Get Binding...

Mark Baker <[email protected]> Sun, 29 Dec 2002 16:01:09 -0500
Newsgroups gmane.comp.windows.devel.soap.general
Message-ID <[email protected]>
On Sat, Dec 28, 2002 at 12:24:07PM -0600, Sievert, James A wrote:
> I've been trying to figure out exactly what a SOAP 1.2 HTTP-GET request
> might look like.  So far, I've seen several examples.  What's not clear from
> any of these examples is how the query string is used.
>
> >From [1] we have the following example:
>
> GET /travelcompany.example.org/reservations?code=FT35ZBQ
>
> What document defines the actual specification for the format of the GET
> binding?  It hasn't exactly jumped out at me from the various SOAP 1.2
> documents.  For example, if the target resource requires multiple
> parameters, how is that represented in the query string?

The URI is opaque from a SOAP POV; query strings, etc.. don't enter into
the equation.  You just invoke GET on it as you would any URI.  The SOAP
1.2 GET binding just describes how a SOAP envelope is returned.

What it sounds like you're looking to do, there isn't a standard for yet.

And FWIW, don't expect GET to fit nicely into how you may have been
using SOAP 1.1.  It's support in SOAP 1.2 has profound architectural
implications that have yet to be appreciated by most.  In a nutshell,
if you've been putting a method/operation in the SOAP envelope over
HTTP, then you've been using SOAP "incorrectly" (at least from the
POV that says that GET support in SOAP is "good").

MB
--
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.