W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

Issue 133, and permitting no body

From: Mark Baker <distobj@acm.org>
Date: Wed, 30 Jan 2002 14:01:42 -0500 (EST)
Message-Id: <200201301901.OAA12408@markbaker.ca>
To: xml-dist-app@w3.org
Hi all,

I had a thought recently, about an extension to our SOAP/HTTP binding
to support the GET method.  I'm *not* suggesting we incorporate this
into the spec, only that we consider its needs going forward, as it
requires a change to the current envelope schema.

AFAIK, no use of HTTP GET today includes a body, though RFC 2616 doesn't
preclude one from being used.  But, it defines no behaviour for what the
body should mean, except implicitly in the definition of GET that it
can't change the meaning of the GET (i.e. can't use the body to change
what the Request-URI identifies).

So, if we used the GET body to carry header information, specifically
SOAP headers, we could use GET in a web architecture friendly manner.
What that means is that a GET binding could permit an envelope in a GET
body, but that envelope would have to be all headers, no body.  However,
currently, the envelope schema requires that there be at least one body.

Would we consider making this change to the envelope to support GET in
the future?

Note that this may help address issue 133.

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Wednesday, 30 January 2002 13:59:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT