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
{{ message }}
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
There can be use cases in which an actor shall only be kept alive as long as there are incoming commands. For it it would be useful to have something similar like the BehaviourContext where a developer can define differing behaviours for commands and events separately.
Currently an actors' receiveTimeout can be configured globally causing an actor kept alive on event as well.
@krasserm Yes, we would like to contribute this enhancement. What's the best way forward here? Shall we create a small draft how we would implement this so you can comment on this first before implementation?
Maybe you already have an idea? At a first glimpse i had the idea to do something similar like the "BehaviourContext" or even re-use/extend the "BehaviourContext". What do you think?
@ermanito Glad to hear you're planning a contribution. I don't have a detailed implementation in mind yet but modifying BehaviorContext (e.g. adding a setReceiveTimeout method) sounds like a good idea. Let's discuss that more detailed in a first pull request. Looking forward to review it 😃
There can be use cases in which an actor shall only be kept alive as long as there are incoming commands. For it it would be useful to have something similar like the BehaviourContext where a developer can define differing behaviours for commands and events separately.
Currently an actors' receiveTimeout can be configured globally causing an actor kept alive on event as well.
@krasserm What do you think?
The text was updated successfully, but these errors were encountered: