[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
-----Original Message-----
From: Andrea Westerinen [mailto:andreaw@cisco.com]
Sent: Thursday, September 25, 2003 11:52 AM
To: 'Shel Finkelstein'; wsdm@lists.oasis-open.org
Subject: [wsdm] Thoughts on "transaction" wording for MUWS
My apologies for being so late on this. And, Shel did not get a
chance to review.Section Heading - Collections of Management
Actions and Transactions[TRANS.001] MUST support the definition of
a "unit of work" that consists of multiple actions against a
single device[TRANS.002] MAY support the definition of a "unit of
work" that consists of multiple actions against multiple
devices[TRANS.003] MUST report status, errors or lack of support
for execution of collection of actions against one or more
devices[TRANS.004] MAY support actions of commit and rollback of
multiple actions against one or more devices[TRANS.005]
SHOULD support time-out of the "unit of work" consisting of
multiple actions against one or more devices[TRANS.006] SHOULD
support user-defined preferences related to the execution of the
"unit of work" consisting of multiple actions against one or more
devices. [TRANS.006.1] User preferences SHOULD include whether
the desired behavior is "all or nothing"Andrea
--------------91A32BD988876013E205A5D3
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
+1 to Andrea's comments.
<p>ACID transactions aren't required, and I believe that they're inappropriate
over the internet. But when they are available and appropriate, transactions
have significant semantic value, but they do affect the client model (e.g.,
dealing with rollback as a command or rolledback as an outcome.
<p>Shel
<p>-------- Original Message --------
<table BORDER=0 CELLSPACING=0 CELLPADDING=0 >
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Subject: </th>
<td>RE: [wsdm] Thoughts on "transaction" wording for MUWS</td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Date: </th>
<td>Mon, 29 Sep 2003 20:34:50 -0700</td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>From: </th>
<td>"Andrea Westerinen" <andreaw@cisco.com></td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>To: </th>
<td>"'Jeff Bohren'" <jbohren@opennetwork.com>, <[email protected]></td>
</tr>
</table>
<br> <span class=134572703-30092003><font face="Arial"><font color="#0000FF"><font size=-1>Jeff,
The rewording that Shel and I did, tried to clarify these points.
Also, I did mean to distinguish between collections of actions and transactions
(hence the commit/rollback terminology that morphed into atomic transactions
with Shel's help). Note, however, that atomic transactions are NOT
specified as MUST. </font></font></font></span><span class=134572703-30092003></span><span class=134572703-30092003><font face="Arial"><font color="#0000FF"><font size=-1>I
believe that a client DOES want (and wants to be aware of) transactional
processing, at various points in managing a service. If a client
needs atomicity, then it should be definable. If the service can't
support that, so be it. An error needs to be returned. However,
I believe that a client will want to take advantage of atomic transactions
(in certain circumstances) versus having to dealing with error scenarios
and "best effort" rollback on their own.</font></font></font></span><span class=134572703-30092003></span><span class=134572703-30092003><font face="Arial"><font color="#0000FF"><font size=-1>Andrea</font></font></font></span><span class=134572703-30092003></span>
<div class="OutlookMessageHeader" lang="en-us" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Jeff Bohren [<A HREF="mailto:jbohren@opennetwork.com";>mailto:jbohren@opennetwork.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Thursday, September
25, 2003 11:19 AM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> wsdm@lists.oasis-open.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> RE: [wsdm] Thoughts
on "transaction" wording for MUWS</font></font>
<br> </div>
<span class=093031018-25092003><font face="Arial"><font color="#0000FF"><font size=-1>From
the discussions so for it seems we are not really talking about transactions.
What we really mean is a batch of operations that may be invoked on a MUWS
service. It that context the term "Collections on Management Actions" makes
sense to me, but I would leave off the "and Transactions". </font></font></font></span><span
class=093031018-25092003></span><span class=093031018-25092003><font face="Arial"><font color="#0000FF"><font size=-1>I
would also leave out the notion of explicit commit or rollback support.
A MUWS service may or may not use transactions when processing a
batch of operations (i.e. Collection of Management Actions), but that should
not be an issue the MUWS client needs to be aware of.</font></font></font></span><span
class=093031018-25092003></span><span class=093031018-25092003><font face="Arial"><font color="#0000FF"><font size=-1>Use
of the terms "Transaction", "Commit", or "Rollback" is going to interpreted
as meaning we are requiring transaction support rather than batch operation
support. I don't normally get hung up on wording, but these are extremely
loaded terms.</font></font></font></span> <font face="Arial"><font size=-1>Jeff
Bohren</font></font><font face="Arial"><font size=-1>Product Architect</font></font><font face="Arial"><font size=-1>OpenNetwork
Technologies, Inc</font></font>
<blockquote dir=ltr style="MARGIN-RIGHT: 0px">
<div class="OutlookMessageHeader" lang="en-us" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Andrea Westerinen [<A HREF="mailto:andreaw@cisco.com";>mailto:andreaw@cisco.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Thursday, September
25, 2003 11:52 AM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> 'Shel Finkelstein'; wsdm@lists.oasis-open.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> [wsdm] Thoughts on
"transaction" wording for MUWS</font></font>
<br> </div>
<span class=943095507-25092003><font face="Arial"><font size=-1>My apologies
for being so late on this. And, Shel did not get a chance to review.</font></font></span><span
class=943095507-25092003></span><span class=943095507-25092003><font face="Arial"><font size=-1>Section
Heading - Collections of Management Actions and Transactions</font></font></span><span
class=943095507-25092003></span><span
class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.001]
MUST support the definition of a "unit of work" that consists of multiple
actions against a single device</font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.002]
MAY support the definition of a "unit of work" that consists of multiple
actions against multiple devices</font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.003]
MUST </span><span
class=943095507-25092003>report status, errors
or lack of support for execution of collection of actions against one or
more devices</font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.004]
MAY support actions of commit and </span><span
class=943095507-25092003>rollback
of multiple actions against one or more devices</font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.005]
SHOULD </span><span
class=943095507-25092003>support time-out of
the "unit of work" consisting of multiple actions against one or more devices</font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>[TRANS.006]
SHOULD support user-defined preferences related to the execution of the
"unit of work" consisting of multiple actions against one or more devices. </font></font></span><span class=943095507-25092003><font face="Arial"><font size=-1>
[TRANS.006.1] User preferences SHOULD include whether the desired behavior
is "all or nothing"</font></font></span><span
class=943095507-25092003></span><span
class=943095507-25092003><font face="Arial"><font size=-1>Andrea</font></font></span><span
class=943095507-25092003></span><span
class=943095507-25092003></span></blockquote>
</html>
--------------91A32BD988876013E205A5D3--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]