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

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
>