raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

Adding docs about how to do remoting with TypedActors

Browse source
This commit is contained in:
Viktor Klang 2012-02-27 15:18:45 +01:00
parent 572382b220
commit b9359a82a6
2 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
akka-docs/java/typed-actors.rst
View file

@ -180,3 +180,9 @@ By having your Typed Actor implementation class implement any and all of the fol
* ``TypedActor.PostRestart`` * ``TypedActor.PostRestart``
You can hook into the lifecycle of your Typed Actor. 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``.

10
akka-docs/scala/typed-actors.rst
View file

@ -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, This allows you to react to DeathWatch ``Terminated``-messages and other types of messages,
e.g. when interfacing with untyped actors. 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 Supercharging
------------- -------------