Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use ActorSelections for remote nodes in Membership #98

Open
clinedome-work opened this issue Aug 12, 2014 · 0 comments
Open

Use ActorSelections for remote nodes in Membership #98

clinedome-work opened this issue Aug 12, 2014 · 0 comments

Comments

@clinedome-work
Copy link
Collaborator

Sirius currently attempts to resolve ActorRefs for each node in the MembershipActor, and store those refs for use by any actor within the system for communicating with remote nodes. These refs aren't necessarily long-lived, and maintaining them is a pain.

Instead of resolving ActorRefs and maintaining them in the MembershipMap, we should instead store ActorSelections. When an actor needs to initiate a session of communication with a remote node, it can resolve a ref from the selection -- or, more likely, simply send a message via the selection and implicitly get the ref for future use when the remote node responds.

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

No branches or pull requests

1 participant