[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsdm][UPlat] Transaction
What?
A “unit of work” that consists of multiple actions against a single resource, the same action applied to multiple resources, or multiple actions against multiple resources. The “unit of work” should be executed once and only once, even if due to transmission failures or other errors, the request may be received multiple times. When supported by the manageability provider, rollback of the action may be requested. This would be done upon failure of one or more of the actions in the "unit of work".
A UML diagram describing a transaction model is attached.
Why?
Grouping actions against resources and assuring their execution is very valuable. A manager may request that multiple actions/operations be performed, and that the integrity of the complete/combined request be preserved. For example, it is important for efficient operation to shutdown and failover a jabbering port, and not have the shutdown request arrive multiple times, after the port error has been corrected.
Note that transactions are a part of regular Web Services. Manageability implementations would make use of existing Wes Services transactional capabilities.
Andrea
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]