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

Serializing ActorRef? #6

Open
rogeralsing opened this issue May 18, 2016 · 1 comment
Open

Serializing ActorRef? #6

rogeralsing opened this issue May 18, 2016 · 1 comment

Comments

@rogeralsing
Copy link

rogeralsing commented May 18, 2016

Hi,
Are you planning to make ActorRef serializable when/if you create networking support?

This has been one of the most problematic things for us when creating Akka.NET (port of Akka to .NET).
Polymorphic serialization is hard and depending on serializer and platform not always possible.
(LocalActorRef, DeadLetterActorRef, RemoteActorRef, RouterActorRef etc etc)

In my other actor project https://github.com/rogeralsing/gam, I ditched the ActorRef concept and used a more Erlang like PID which is a simple value that instead of using polymorphism, resolves the underlying actor.
This way, the actor pid can easily be passed across the wire using e.g. protobuf as the serializer.

Just wanted to give a heads up on that one.
Another benefit of the above approach would be the possibility of cross platform Go <-> Rust remoting, hint hint

If you are still going down the ActorRef route, are there some interesting ways that Rust can deal with the above?

@yenwel
Copy link

yenwel commented Jan 16, 2017

+1 for this one. 0mq does this also.

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

No branches or pull requests

2 participants