- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Mon, 13 Feb 2006 12:54:43 -0800
- To: David Orchard <dorchard@bea.com>
- CC: public-ws-addressing@w3.org
2 editorial (I hope) comments below. -Anish -- David Orchard wrote: > I had an action to wordsmith the new binding around "response". My best > attempt is: > > > > This SOAP 1.1 request optional response HTTP binding, in conjunction > with the SOAP 1.1 binding, can be used for sending request messages with > an optional SOAP response. This binding augments the SOAP 1.1 binding > by allowing that the HTTP [RFC 2616] response MAY have a 202 status code > and the response body MAY be empty. Note that the HTTP [RFC 2616] > specification states "the 202 response is intentionally non-committal". > As such, any content in the response body, including a SOAP body, MAY or s/SOAP body/SOAP Envelope/ > MAY not be an expected SOAP response. s/MAY not/MAY NOT/ > > > > Old text: > > This SOAP 1.1 request optional response HTTP binding can be used for > sending request messages with an optional response. For such messages, > the HTTP [RFC 2616] > <file:///C:\Documents%20and%20Settings\dorchard\Local%20Settings\Temporary%20Internet%20Files\OLK6\soap11reqoptresphttpbinding.html#RFC2616#RFC2616> > response MUST be a 202 status code and the response body MAY be empty. > > > > Cheers, > > Dave >
Received on Monday, 13 February 2006 20:55:01 UTC