Thanks for your answer. It was in fact a question from my employer that asked if msm allows to do the same as the last example of the statechart doc : http://www.boost.org/doc/libs/1_44_0/libs/statechart/doc/tutorial.html (at the end of the page). It's not a requirement, just a technical question because from my understanding of UML, state regions should be managed separately and I thought maybe they were threaded in some way. We wanted to be sure of the whole behaviour before starting testing it. Anyway I see that I should treat the state machine like a STL component in regards to thread-safety and asynchronous event management. As it's not a requirement, it's not a problem for me but I was asking myself if there would be an interest in having the event processing being thread-safe, allowing multiple threads to send events? Maybe like haveing a msm2 like signals2? I'm not experienced enough to see if it would be a good idea and I don't need it so it's just a theorical question. On Thu, Aug 26, 2010 at 19:57, Christophe Henry <christophe.j.henry@googlemail.com> wrote:

Hi,

...

from what I understand of Meta-State-Machine library documentation, the state transitions are performed immediately when events are processed. - right?

Right.

...

So my (maybe very dumb) question is : is there cases where the state-machine will perform state transitions in an asynchronous way?

No, transitions are performed when an event is fired.

What are you trying to achieve?

Regards, Christophe _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost