- From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 08 Feb 2006 06:48:22 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv8921
Modified Files:
ws-addr-soap.xml
Log Message:
Added the resolution of CR15/i067/i068 - discussion of anonymous/non-anonymous in SOAP 1.1/SOAP 1.2.
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.107
retrieving revision 1.108
diff -C2 -d -r1.107 -r1.108
*** ws-addr-soap.xml 8 Feb 2006 06:23:49 -0000 1.107
--- ws-addr-soap.xml 8 Feb 2006 06:48:20 -0000 1.108
***************
*** 392,403 ****
reply-to: header is likely to differ from the [reply endpoint] address.</p>
</div2>
- <div2 id="soaphttp">
- <head>Use of Anonymous Address in SOAP</head>
- <p>When <attval>&nsuri;/anonymous</attval> is specified as the address of an EPR, the
- underlying SOAP protocol binding provides a channel to the specified endpoint. Any
- underlying protocol binding supporting the SOAP request-response message exchange pattern
- provides such a channel for response messages. For instance, the SOAP 1.2 HTTP
- binding[<bibref ref="SOAP12-PART2"/>] puts the reply message in the HTTP response.</p>
- </div2>
</div1>
<div1 id="s11ext">
--- 392,395 ----
***************
*** 441,444 ****
--- 433,475 ----
</div2>
</div1>
+ <div1 id="addressesinsoap">
+ <head>Addresses in SOAP</head>
+ <div2 id="anonaddress">
+ <head>Use of Anonymous Address in SOAP</head>
+ <div3>
+ <head>SOAP 1.1/HTTP</head>
+ <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for the response
+ endpoint then there is no change to the SOAP 1.1/ HTTP binding. </p>
+ </div3>
+ <div3>
+ <head>SOAP 1.2</head>
+ <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for the response
+ endpoint and the request is the request part of a SOAP request-response MEP [<bibref
+ ref="SOAP12-PART2"/>], then any response MUST be the response part of the same SOAP
+ request-response MEP [<bibref ref="SOAP12-PART2"/>].</p>
+ </div3>
+ </div2>
+ <div2 id="nonanonaddress">
+ <head>Use of Non-Anonymous Addresses in SOAP</head>
+ <div3>
+ <head>SOAP 1.1/HTTP</head>
+ <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified for the response
+ endpoint, then the request SHOULD be part of a binding that supports not returning a
+ SOAP envelope in the HTTP response. Any response message SHOULD be sent using a separate
+ connection and using the address value specified by response endpoint. Note that other
+ specifications MAY define special URIs that have other behaviours (similar to the
+ anonymous URI).</p>
+ </div3>
+ <div3>
+ <head>SOAP 1.2</head>
+ <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified for the response
+ endpoint, then any response SHOULD not be the response part of the same SOAP
+ request-response MEP [<bibref ref="SOAP12-PART2"/>]. For instance, a SOAP 1.2 HTTP
+ binding that supports a one-way MEP could put the reply message in a separate one-way
+ MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY
+ define special URIs that have other behaviours (similar to the anonymous URI).</p>
+ </div3>
+ </div2>
+ </div1>
<div1 id="faults">
<head>Faults</head>
Received on Wednesday, 8 February 2006 06:48:26 UTC