wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsdm][uplat] Transactions
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: "Andrea Westerinen" <andreaw@cisco.com>,<wsdm@lists.oasis-open.org>
- Date: Thu, 30 Oct 2003 15:34:55 -0500
Title: Message
Can we just say that "reasons to include" are that manager
may request to perform multiple operations on the manageable resource and
integrity of combined request may need to be preserved. Also that transactions
are part of regular WSs and implementations of manageability merely makes use of
those existing capabilities of WSs.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
Definition:
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.
Reasons to
include:
Grouping actions
against resources and assuring their execution/failure is very valuable.
Activities such as IETF's NetConf discuss "transactions". The goal is for
MUWS to be a superset of the functionality in NetConf - avoiding the need for
multiple protocols/solutions in implementations.
Andrea
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]