more classic remoting leftovers
* fix several tests that were using akka.remote.netty.tcp config * replace akka.tcp with akka in more places * some doc cross references to remoting.md
This commit is contained in:
parent
18a3569a7e
commit
71e9bdc262
73 changed files with 284 additions and 322 deletions
|
|
@ -303,11 +303,11 @@ private[akka] class RemoteActorRefProvider(
|
|||
*
|
||||
* Example:
|
||||
*
|
||||
* akka.tcp://sys@home:1234/remote/akka/sys@remote:6667/remote/akka/sys@other:3333/user/a/b/c
|
||||
* akka://sys@home:1234/remote/akka/sys@remote:6667/remote/akka/sys@other:3333/user/a/b/c
|
||||
*
|
||||
* means that the logical parent originates from “akka.tcp://sys@other:3333” with
|
||||
* one child (may be “a” or “b”) being deployed on “akka.tcp://sys@remote:6667” and
|
||||
* finally either “b” or “c” being created on “akka.tcp://sys@home:1234”, where
|
||||
* means that the logical parent originates from “akka://sys@other:3333” with
|
||||
* one child (may be “a” or “b”) being deployed on “akka://sys@remote:6667” and
|
||||
* finally either “b” or “c” being created on “akka://sys@home:1234”, where
|
||||
* this whole thing actually resides. Thus, the logical path is
|
||||
* “/user/a/b/c” and the physical path contains all remote placement
|
||||
* information.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue