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

Re: Work Units clarification question

From: Greg Ritzinger <gritzinger@novell.com>
Date: Thu, 18 Nov 2004 12:08:15 -0700
Message-Id: <s19c90bf.032@sinclair.provo.novell.com>
To: <steve@enigmatec.net>,<public-ws-chor@w3.org>
 
>For example if within such a work-unit 5 sub choreographies are now
>activated when does the parent complete?
>Is it immediately the final sub-choreo starts or is it when the final
>sub-choreo also completes?
 
I propose adding a blocking attrubute for the non-atomic activities. If
the blocking attribute is true then the containing work-unit is not
considered complete until the activity completes, otherwise as soon as
it starts, like a spawn vs. call. By default activities always block.
 
>How does the termination status of a sub-choreo, in this scenario,
>affect the parent (i.e. a sub-choreo goes into an exception block)?
Does it change anything (status quo)? If the sub-choreo does go into an
exception block it may or may not fail, depending upon how the exception
is handled. If it does fail, then isn't this communicated through the
bound variables? 
 
-Greg 

>>>Steve Ross-Talbot <steve@enigmatec.net> 11/18/04 9:58 am >>>

In the defn of a Work-Unit in CDL (latest draft) it says (on page 29 of
the pdf):

A Work Unit completes successfully when all its enclosed actions
complete successfully.

Moving forward a little to consider multiple concurrent participants in
a work unit that might have this new concurrent attribute (and
possibly other things) what does complete successfully mean with
respect to the concurrent activities.

For example if within such a work-unit 5 sub choreographies are now
activated when does the parent complete?
Is it immediately the final sub-choreo starts or is it when the final
sub-choreo also completes?
How does the termination status of a sub-choreo, in this scenario,
affect the parent (i.e. a sub-choreo goes into an exception block)?

Cheers

Steve T
Received on Thursday, 18 November 2004 19:09:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:11 GMT