Possible HTTP GET bindings for SOAP

I think's Tim proposal is interesting.  Perhaps it should be handed to
the XMLP WG (when we've got some time), as we'd probably want to take
it to the developer community first to see if they're interested.  The
XMLP WG has a good relationship with them.

Also, I had a sort-of-proposal[1] to the XMLP WG to build a SOAP binding
to HTTP GET.  It was done tongue-in-cheek, because of the ridiculous
nature of what it entailed (using a body on a GET).  But it would be the
best fit from a structural point of view; basically, use SOAP headers as
extended HTTP headers, just as is done on POST, but not have a SOAP
body ... though you'd still need to use something like M-GET in order to
provide a dispatch hook for the SOAP processing model.

Just pointing it out as an FYI.

A more realistic solution that I've considered is an RFC 822
serialization of the SOAP Envelope.  This would make integration with
HTTP (GET in particular) a lot simpler, as SOAP headers could be
intermixed with HTTP headers.

 [1] http://lists.w3.org/Archives/Public/xml-dist-app/2002Jan/0416.html

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com

Received on Monday, 22 April 2002 01:04:18 UTC