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 did not understand an actor having multiple receiver ; how Actor will know his initial receive state like in this case it is waiting.
The second question is calling "context.become" in waiting state will change actor behavior to "runNext", similar we have done running receiver as well. Why it is not being done in "runNext" and "enqueueJob". The runNext and enqueueJob is calling running(queue) as function call not as change in behavior.
I am new learner for Akka, did not see any code where receiver is called as function instead of conext.become.
Regards,
Arun
The text was updated successfully, but these errors were encountered:
Hi,
I did not understand an actor having multiple receiver ; how Actor will know his initial receive state like in this case it is waiting.
The second question is calling "context.become" in waiting state will change actor behavior to "runNext", similar we have done running receiver as well. Why it is not being done in "runNext" and "enqueueJob". The runNext and enqueueJob is calling running(queue) as function call not as change in behavior.
I am new learner for Akka, did not see any code where receiver is called as function instead of conext.become.
Regards,
Arun
The text was updated successfully, but these errors were encountered: