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

Re: Optional SOAP response; the transfer binding view

From: <noah_mendelsohn@us.ibm.com>
Date: Wed, 11 Jan 2006 10:57:25 -0500
To: Mark Baker <distobj@acm.org>
Cc: xml-dist-app@w3.org
Message-ID: <OF86DEB8AF.1EDC87E6-ON852570F3.00575C8D-852570F3.0057A7B6@lotus.com>

I think the redraft I posted at [1] is consistent with the assumptions and 
conclusions in your note.  Specifically, the inboundMessage and 
outputBoundMessage properties continue to consistent of the entire SOAP 
level message, including things like the WebMethod when appropriate.  All 
that's changed is that (a) the request/response MEP makes clear that the 
response messages for that MEP need not contain a SOAP envelope and (b) 
the HTTP binding makes clear that the correct embodiment of an otherwise 
successful "no envelope" response is an status code of 202.

Noah

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

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Received on Wednesday, 11 January 2006 15:57:40 GMT

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