A comparison of Web services transaction protocols compares how different transaction protocols may be applied to solve specific business problems and transactions in a Web services World describing how the model defined in these specifications work. At Contempo technologies, we provide the appropriate web transaction specification for all our customers.

The various web transaction specifications are:

WS-Business Activity
This business activity specification provides the definition of the business activity coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines two specific agreement coordination protocols for the business activity coordination type: Business Agreement with Participant Completion and Business Agreement with Coordinator Completion. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of long-running distributed activities.

Ws-atomic transaction
The atomic transaction defines three specific agreement coordination protocols for the atomic transaction coordination type: completion, volatile two-phase commit, and durable two-phase commit. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of short-lived distributed activities that have the all-or-nothing property.

Ws-coordination
It describes an extensible framework for providing protocols that coordinate the actions of distributed applications. It supports a number of applications, including those that need to reach consistent agreement on the outcome of distributed activities. Additionally this specification describes a definition of the structure of context and the requirements for propagating context between cooperating services.

Ws-transaction
It defines the coordination type that is used with the coordination framework and it defines two coordination types such as atomic transaction and business activity transaction. Developers can use both of these types when building the application.

Ws-CAF
It defines an open frame work for applications that contain multiple services and the various benefits of ws-caf are, it co-ordinates the context information, define the relationship of co-coordinators and interact multiple transaction models.

Ws-context
It relates a set of interaction between web services and it is typically used in the header of soap message. It also provides means to a shared reference context.

For more information on our Transaction Specifications, Contact us at webmaster@contempotech.com.