You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looked at the code because I saw that when the first event is sent, the thread which is the owner of the state machine is blocked until the whole chain of events is fully consumed.
Is there any possibility to update it in order to make the statemachine fully managed by a separate thread?
The text was updated successfully, but these errors were encountered:
I would be interested in the also.
Currently I am thinking that I would run the whole state machine in a separate thread, and that I have to queue the incoming event myself?
The best approach depends on the demand. Since we don't have an internal loop that "run forever", one can implement that method that reads from a stream of events and send the events to the state machine, and this method can live in a dedicated thread.
Do you have a problem idea so I can work on an example?
Hi there,
I looked at the code because I saw that when the first event is sent, the thread which is the owner of the state machine is blocked until the whole chain of events is fully consumed.
Is there any possibility to update it in order to make the statemachine fully managed by a separate thread?
The text was updated successfully, but these errors were encountered: