i067 and i068 proposal: update SOAP binding document

Here's a proposal for i067 and i068 that changes the WS-Addressing SOAP
binding document.  There are two possibilities: the soap 1.1 http
binding specification is by value in this document, or by reference to a
separate document


3.5 Use of Anonymous Address in SOAP


When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for
the response endpoint, the underlying SOAP protocol binding provides a
channel to the specified endpoint. Any underlying protocol binding
supporting a request-response message exchange pattern provides such a
channel for response messages. For instance, the SOAP 1.2 HTTP
binding[SOAP 1.2 Part 2: Adjuncts
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2004/ws/addressing/ws-addr-soap
.html#SOAP12-PART2#SOAP12-PART2> ] puts the reply message from the SOAP
request-response MEP in the HTTP response.

 


3.6 Anonymous Address not used in SOAP


When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified
for the response endpoint, the underlying SOAP protocol binding is not
used as a channel to the specified endpoint.  An additional underlying
protocol binding provides a channel for response messages.  For
instance, a SOAP 1.2 HTTP binding that supports a one-way MEP could put
the reply message in a separate HTTP request.

 


4. SOAP 1.1 Addressing 1.0 Extension


The SOAP 1.1 Addressing 1.0 Extension defines a set of SOAP header
blocks and SOAP 1.1 HTTP Binding modification to support the SOAP 1.2
Addressing 1.0 Feature described in 2. SOAP 1.2 Addressing 1.0 Feature
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2004/ws/addressing/ws-addr-soap
.html#s12feature#s12feature> .  This SOAP 1.1 extension is provided for
backwards compatibility only.

 


V1: Addition to 4.2 Description


The SOAP 1.2 Addressing 1.0 Feature changes the SOAP 1.1/HTTP binding
when "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified
for the response endpoint.  In this case, the receiver of a message MUST
respond with an HTTP response message.  One possibility is a 202 status
code and an empty HTTP body, aka no SOAP envelope.  If a value other
than "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for
the response endpoint, the outbound message MUST be sent using a
separate connection using the address value of the specified by
appropriate response endpoint 

 


V2: Addition to 4.2 Description


The SOAP 1.2 Addressing 1.0 Feature changes the SOAP 1.1/HTTP binding
when "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified
for the response endpoint.  In this case, the SOAP 1.1 one-way HTTP
Binding [@@] is in effect.