improve documentation of explicitly given routees
This commit is contained in:
parent
916c2d4d11
commit
9ac11a6432
5 changed files with 16 additions and 6 deletions
|
|
@ -33,6 +33,11 @@ You can also give the router already created routees as in:
|
|||
|
||||
.. includecode:: code/akka/docs/routing/RouterViaProgramExample.scala#programmaticRoutingRoutees
|
||||
|
||||
It should be noted that no actor factory or class needs to be provided in this
|
||||
case, as the ``Router`` will not create any children on its own (which is not
|
||||
true anymore when using a resizer). The routees can also be specified by giving
|
||||
their path strings.
|
||||
|
||||
When you create a router programmatically you define the number of routees *or* you pass already created routees to it.
|
||||
If you send both parameters to the router *only* the latter will be used, i.e. ``nrOfInstances`` is disregarded.
|
||||
|
||||
|
|
@ -48,7 +53,7 @@ Once you have the router actor it is just to send messages to it as you would to
|
|||
|
||||
router ! MyMsg
|
||||
|
||||
The router will apply its behavior to the message it receives and forward it to the routees.
|
||||
The router will forward the message to its routees according to its routing policy.
|
||||
|
||||
Remotely Deploying Routees
|
||||
**************************
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue