- From: Rogers, Tony <Tony.Rogers@ca.com>
- Date: Mon, 16 Jan 2006 10:59:53 +1100
- To: "David Orchard" <dorchard@bea.com>, "WS-Addressing" <public-ws-addressing@w3.org>
- Message-ID: <BEE2BD647C052D4FA59B42F5E2D946B307BCC9@AUSYMS12.ca.com>
While we're messing with 3.4.1, I'd like to change "...an address that is different than..." to "...an address that is different from...". The latter is correct in all dialects of the English, the former only in some :-) Tony Rogers tony.rogers@ca.com <blocked::mailto:tony.rogers@ca.com> ________________________________ From: public-ws-addressing-request@w3.org [mailto:public-ws-addressing-request@w3.org] On Behalf Of David Orchard Sent: Saturday, 14 January 2006 7:44 To: WS-Addressing Subject: i68 and i69 proposal for WSDL doc Here's a proposal for how the WSDL binding doc would refer to external documents. I had to really really squint hard to convince myself that "Indicating use of WS-Addressing" is the right section for soap binding/mep changes.. I mean, really really really hard. 3.4 Non-anonymous indicated This section describes the Message Exchange Patterns and binding changes when WS-Addressing is indicated. 3.4.1 SOAP 1.1/HTTP binding WS-Addressing changes the SOAP 1.1/HTTP binding when the value of the response endpoint EPR contains an address that is different than the anonymous URI. In this case, the receiver of a message MUST respond with a 202 status code and an empty HTTP body, aka no SOAP envelope. If the value of the response endpoint EPR contains an address that is different than the anonymous URI, the outbound message MUST be sent using a separate connection using the address value of the specified by appropriate response endpoint 3.4.2 SOAP 1.2 binding When the value of the response endpoint EPR contains the anonymous address, then the inbound and any outbound message are part of a single SOAP request-response MEP [soap 1.2 adjuncts ref]. When the value of the response endpoint EPR does not contain the anonymous address, then any outbound message is not part of the mep that the inbound message is in.
Received on Monday, 16 January 2006 00:00:21 UTC