- From: <noah_mendelsohn@us.ibm.com>
- Date: Thu, 31 Jan 2002 22:37:26 -0500
- To: distobj@acm.org
- Cc: xml-dist-app@w3.org
I would have thought that the approriate way to map SOAP to HTTP GET would be to encode the SOAP Envelope in the request URI. Note that our current design makes no requirement that the binding serialize the envelope using xml 1.0 "<...>" syntax, so there would be considerable lattitude to use URI-friendly representations of the infoset. The major problem I see is the traditional limitation on URI length, which is arguably a deficiency of Web deployment and not of SOAP itself. I think that many of the sorts of SOAP messages that one would reasonably want to send via GET would be representable with moderate length URI's. Taking the SOAP body out of the envelope seems to seriously undercut the fundamental semantics of SOAP. Encoding the entire envelope in URI lets us do the right thing, which is to have the SOAP envelope affect the semantics of the GET. ------------------------------------------------------------------ Noah Mendelsohn Voice: 1-617-693-4036 IBM Corporation Fax: 1-617-693-8676 One Rogers Street Cambridge, MA 02142 ------------------------------------------------------------------
Received on Thursday, 31 January 2002 22:51:49 UTC