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

Clarifying in the docs that the user gets an ActorRef and not a RoutedActorRef

Browse source
This commit is contained in:
Viktor Klang 2012-08-30 18:09:31 +02:00
parent 4c859420d1
commit d209247b7f
2 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
akka-docs/java/routing.rst
View file

@ -75,7 +75,8 @@ How Routing is Designed within Akka
Routers behave like single actors, but they should also not hinder scalability. Routers behave like single actors, but they should also not hinder scalability.
This apparent contradiction is solved by making routers be represented by a This apparent contradiction is solved by making routers be represented by a
special :class:`RoutedActorRef`, which dispatches incoming messages destined special :class:`RoutedActorRef` (implementation detail, what the user gets is
an :class:`ActorRef` as usual) which dispatches incoming messages destined
for the routees without actually invoking the router actor’s behavior (and thus for the routees without actually invoking the router actor’s behavior (and thus
avoiding its mailbox; the single router actor’s task is to manage all aspects avoiding its mailbox; the single router actor’s task is to manage all aspects
related to the lifecycle of the routees). This means that the code which decides related to the lifecycle of the routees). This means that the code which decides

3
akka-docs/scala/routing.rst
View file

@ -75,7 +75,8 @@ How Routing is Designed within Akka
Routers behave like single actors, but they should also not hinder scalability. Routers behave like single actors, but they should also not hinder scalability.
This apparent contradiction is solved by making routers be represented by a This apparent contradiction is solved by making routers be represented by a
special :class:`RoutedActorRef`, which dispatches incoming messages destined special :class:`RoutedActorRef` (implementation detail, what the user gets is
an :class:`ActorRef` as usual) which dispatches incoming messages destined
for the routees without actually invoking the router actor’s behavior (and thus for the routees without actually invoking the router actor’s behavior (and thus
avoiding its mailbox; the single router actor’s task is to manage all aspects avoiding its mailbox; the single router actor’s task is to manage all aspects
related to the lifecycle of the routees). This means that the code which decides related to the lifecycle of the routees). This means that the code which decides