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

ActorRef passing is somewhat limited. #53

Open
pct-cclausen opened this issue Dec 10, 2020 · 0 comments
Open

ActorRef passing is somewhat limited. #53

pct-cclausen opened this issue Dec 10, 2020 · 0 comments

Comments

@pct-cclausen
Copy link

Currently ActorRefs can be passed to Actor calls, but when using forked or threaded actors, this only is correctly handled for a few cases:

  • As a method parameter value
  • As a value in customParameters.

Nesting is not supported at all, so passing a method parameter of types {a: ActorRef, b: ActorRef} fails.
Additionally you can also not return ActorRefs from actor methods.
There are workaround, but they are cumbersome.
I think bus messages also cannot transport ActorRefs.

It would make some scenarios easier to handle to add handling in more cases.

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

2 participants