W3C home > Mailing lists > Public > public-ws-addressing@w3.org > February 2006

Wordsmithing for SOAP 1.1 request optional response HTTP Binding.

From: David Orchard <dorchard@bea.com>
Date: Mon, 13 Feb 2006 11:50:48 -0800
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9CAD0E5A@repbex01.amer.bea.com>
To: <public-ws-addressing@w3.org>
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
MAY not be an expected SOAP response.

 

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\Tempora
ry%20Internet%20Files\OLK6\soap11reqoptresphttpbinding.html#RFC2616#RFC2
616>  response MUST be a 202 status code and the response body MAY be
empty.

 

Cheers,

Dave
Received on Monday, 13 February 2006 19:52:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:11 GMT