W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

Re: Events and States (was: timeouts & states (was: Abstract Bindable Choreography))

From: Assaf Arkin <arkin@intalio.com>
Date: Fri, 11 Apr 2003 10:15:44 -0700
Message-ID: <3E96F840.4060505@intalio.com>
To: Ricky Ho <riho@cisco.com>
CC: jdart@tibco.com, Cummins Fred A <fred.cummins@eds.com>, public-ws-chor@w3.org

Ricky Ho wrote:

>
> In David's example, "State" is not mutually exclusive.  (Correct me if 
> I'm wrong).  A role can have multiple "states" at the same time and 
> each of this state can accept different events and transition to 
> another states.  Somewhat similar to a multi-thread scenario.  So when 
> one thread reaches an end state.  The choreography can still be active 
> because of other threads.
>
> This is quite different from the traditional state chart who try to 
> avoid composite states.  Am I totally lost ?

Some state transition models have mutually exclusive states.

Statechart diagrams have composite states, so they allow for 
non-exclusive states and multiple concurrent sub-states as part of the 
same parent state.

arkin

>
> Rgds, Ricky
>
Received on Friday, 11 April 2003 13:17:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:58 UTC