Question: Actor vs. State Machine Mode

[hirschenberger]

Hey,

I have a general design question: As I understand it, there's two "modes" in crb, it can either be in actor or state-machine mode. When in state-machine mode, no messages are processed before crb enters actor-mode, right? The actor-mode can be also be seen as a state.

So while doing some work in a state, crb can't react on any message, until the state is finished and transitions to actor-mode.

Isn't it error prone to make the user "poll" for new messages by manually going to actor mode and break the state-machine transitioning sequence? What if the user forgets to go to actor mode to wait for an event and transitions to another state, the whole crb will be stuck, or?

In general, where's the usecase for transitioning between states without any external events other than encapsulation?