This post originated from an RSS feed registered with .NET Buzz
by Christian Weyer.
Original Post: Web services transactions made more explicit
Feed Title: Christian Weyer: Web Services & .NET
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/cweyer/Rss.aspx
Feed Description: Philosophizing about and criticizing the brave new world ...
The OASIS XML Cover Pages report that the protagonists of WS-Coordination and WS-Transaction have updated their specs to make the distinction between atomic (ACID) transactions and long running business activities more explicit:
A revised version of the Web Services Coordination (WS-Coordination) specification has been published, together with a new Web Services Atomic Transaction (WS-AtomicTransaction) specification. A third specification Web Services Business Activity (WS-BusinessActivity) is to be released separately to complete the new three-part Web Services Transaction framework from Microsoft, BEA, and IBM. WS-AtomicTransaction "replaces part I of the WS-Transaction specification released in August 2002; the specification titled WS-BusinessActivity will replaces part II of WS-Transaction. WS-Coordination "defines the protocols for creating activities, registering in activities, and transmitting information to disseminate an activity. WS-Coordination provides an extensible framework in which participants can join in activities enabling the coordination of distributed applications." WS-AtomicTransaction "defines the Atomic Transaction coordination type and is appropriate to use when building applications that require a consistent agreement on the outcome of a short-lived distributed activity, where strong isolation is required until the transaction completes." WS-BusinessActivity "defines the Business Activity coordination type. It is appropriate to use when building applications that require a consistent agreement on the coordination of a distributed activity, where strong isolation is not feasible, and application-specific compensating actions are used to coordinate the activity."
The new specs can be found e.g. on Microsoft's server, but the WS-BusinessActivity spec does not yet show up:
WS-Coordination defines the protocols for creating activities, registering in activities, and transmitting information to disseminate an activity. WS-Coordination provides an extensible framework in which participants can join in activities enabling the coordination of distributed applications. Activities can support arbitrary behaviors expressed in terms of protocols including agreement coordination behaviors. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed transactions. The framework enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary protocols and to operate in a heterogeneous and federated environment. Additionally, this specification describes a definition of the structure of context and the requirements for propagating context between cooperating services.
WS-AtomicTransaction defines the Atomic Transaction coordination type. It is appropriate to use when building applications that require a consistent agreement on the outcome of a short-lived distributed activity, where strong isolation is required until the transaction completes. This specification replaces Part I (AT) of the previously released WS-Transaction specification.
WS-BusinessActivity defines the Business Activity coordination type. It is appropriate to use when building applications that require a consistent agreement on the coordination of a distributed activity, where strong isolation is not feasible, and application-specific compensating actions are used to coordinate the activity. This specification replaces Part II (BA) of the previouslyreleased WS-Transaction specification.
Previous Topic
