[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed updates to Doug's text
Here are my suggested edits, incorporating Paul Cotton's second point. Since the message exchange pattern use by MakeConnection is an unusual pattern, the following points need to be reiterated for clarification: ● The MakeConnection message is logically part of a one-way operation; there is no reply message to the MakeConnection itself, and any response flowing on the HTTP backchannel is a pending message. ●Since there is no reply message to MakeConnection, the WS-Addressing specific rules in Section 3.4 “Formulating a Reply Message” are not used. Therefore the value of any wsa:ReplyTo element in the MakeConnection message has no effective impact since the WS-Addressing [reply endpoint] property that is set by the presence of wsa:RepyTo is not used. ● In the absence of any pending message, there will be no message transmitted on the transport back-channel. E.g. In the HTTP case, just an HTTP 202 Accepted will be returned without any SOAP envelope in the HTTP response message. ● When there is a message pending, it is sent on the transport back-channel, using the connection that has been initiated by the MakeConnection request. * The MakeConnection message and operation is deliberately excluded from the WSDL in Appendix B, as this behaviour can only be partially captured using WSDL. Paul
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]