- From: Gaertner, Dietmar <Dietmar.Gaertner@softwareag.com>
- Date: Thu, 7 Mar 2002 14:32:47 +0100
- To: "'xmlp-comments@w3.org'" <xmlp-comments@w3.org>
- Cc: "'dug@us.ibm.com'" <dug@us.ibm.com>
Hi all, the XMLP WG has decided to close the issue 154, invariance of role [1], with the resolution proposed in [2] as follows: Section 2.6 of SOAP Version 1.2 Part 1 now states: "This section sets out the rules by which SOAP messages are processed. Unless otherwise stated, processing must be semantically equivalent to performing the following steps separately, and in the order given. Note however that nothing in this specification should be taken to prevent the use of optimistic concurrency, roll back, or other techniques that might provide increased flexibility in processing order as long as all SOAP messages, SOAP faults and application-level side effects are equivalent to those that would be obtained by direct implementation of the following rules in the order shown below. 1. Determine the set of roles in which the node is to act. The contents of the SOAP envelope, including header blocks and the body, MAY be inspected in making such determination." ... Summarised, this resolution states that a node is explicitly allowed to inspect the message contents when deciding on the set of roles it is to play. A node is also allowed to change the set of roles it plays after starting to process blocks provided that the outcome of this is "semantically equivalent to performing the following steps separately, and in the order given". [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x154 [2] http://lists.w3.org/Archives/Public/xml-dist-app/2002Feb/0392.html
Received on Thursday, 7 March 2002 08:33:01 UTC