Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Separate receiveTimeouts for commands and events #264

Open
agido-hundt opened this issue May 24, 2016 · 3 comments
Open

Separate receiveTimeouts for commands and events #264

agido-hundt opened this issue May 24, 2016 · 3 comments

Comments

@agido-hundt
Copy link
Contributor

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?

@krasserm
Copy link
Contributor

@ermanito this sounds like a useful addition. Do you plan making a contribution?

@agido-hundt
Copy link
Contributor Author

@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?

@krasserm
Copy link
Contributor

@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 😃

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants