W3C home > Mailing lists > Public > public-ws-chor@w3.org > December 2004

Re: ws-chor 12/8/2004: My Comments through 2.5.2

From: Monica Martin <Monica.Martin@Sun.COM>
Date: Wed, 08 Dec 2004 16:25:42 +0100
To: Haugen Robert <Robert.Haugen@choreology.com>
Cc: public-ws-chor@w3.org
Message-id: <1703b141ae.141ae1703b@bur-mail2.east.sun.com>

Bob,
The existing sentence is counterintuitive. Undo to me means you can undo not that something is not enabled to do so. The sentence talks about when you would see a common pattern using undo. And what is that common pattern?
> > page 37
> > From: "One "undo" Finalizer Block along with a "close" Finalizer 
> Block
> > to signal that the "undo" Finalizer Block is no longer able to be
> enabled, 
> > that is, the Choreography is now closed."
> > To: "One "undo" Finalizer Block along with a "close" Finalizer 
> Block 
> > to signal that the "undo" Finalizer Block is enabled, that is, 
> the 
> > Choreography is now closed."
> > Otherwise, if the completed state has been realized and the
> choreography 
> > completed unsuccessfully where the enclosed choreographies were
> closed, 
> > the Finalizer Block will not be installed."
> 
> > Reasoning is it is counterintuition to have the undo specify the
> choreography 
> > is no longer available for undo. You have specified the case where
> enclosed 
> > choreographies could be completed by directon of an enclosing
> choreography. 
> > If this is the case you cite, please explain in the corresponding
> section 
> > referenced above or use my tentative text to clarify.
> 
> I don't understand how the original statement says that the undo
> specifies that the choreography is no longer available for undo.  The
> original statement is at least trying to say that is the role of the
> close finalizer.
> 
> In the original ("From:") statement above, the firing of the "close"
> finalizer signals that the "undo" finalizer can no longer be enabled
> (fired), because the choreography is now closed.  A "close" finalizer
> can make the use of "undo" finalizers more efficient, because it 
> allowsresources to be released before the close of the root 
> choreography.
> Maybe it's a typo, but your "To:" statement says that the "close"
> finalizer signals that the "undo" finalizer is enabled.  Did you mean
> "disabled"?
> 
> Or is the use of "enabled" to mean "fired" or "invoked" confusing?
> 
Received on Wednesday, 8 December 2004 15:25:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:06 UTC