Adding docs about how to do remoting with TypedActors
This commit is contained in:
parent
572382b220
commit
b9359a82a6
2 changed files with 16 additions and 0 deletions
|
|
@ -180,3 +180,9 @@ By having your Typed Actor implementation class implement any and all of the fol
|
|||
* ``TypedActor.PostRestart``
|
||||
|
||||
You can hook into the lifecycle of your Typed Actor.
|
||||
|
||||
Proxying
|
||||
--------
|
||||
|
||||
You can use the ``typedActorOf`` that takes a TypedProps and an ActorRef to proxy the given ActorRef as a TypedActor.
|
||||
This is usable if you want to communicate remotely with TypedActors on otehr machines, just look them up with ``actorFor`` and pass the ``ActorRef`` to ``typedActorOf``.
|
||||
|
|
|
|||
|
|
@ -181,6 +181,16 @@ all messages that are not ``MethodCall``s will be passed into the ``onReceive``-
|
|||
This allows you to react to DeathWatch ``Terminated``-messages and other types of messages,
|
||||
e.g. when interfacing with untyped actors.
|
||||
|
||||
Proxying
|
||||
--------
|
||||
|
||||
You can use the ``typedActorOf`` that takes a TypedProps and an ActorRef to proxy the given ActorRef as a TypedActor.
|
||||
This is usable if you want to communicate remotely with TypedActors on otehr machines, just look them up with ``actorFor`` and pass the ``ActorRef`` to ``typedActorOf``.
|
||||
|
||||
.. note::
|
||||
|
||||
The ActorRef needs to accept ``MethodCall`` messages.
|
||||
|
||||
Supercharging
|
||||
-------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue