transparent remoting -> location transparency
This commit is contained in:
parent
987a8cc2ee
commit
fd4b4e3fb3
5 changed files with 14 additions and 10 deletions
|
|
@ -100,7 +100,7 @@ Physical Actor Paths
|
|||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
While the logical actor path describes the functional location within one actor
|
||||
system, configuration-based transparent remoting means that an actor may be
|
||||
system, configuration-based remote deployment means that an actor may be
|
||||
created on a different network host as its parent, i.e. within a different
|
||||
actor system. In this case, following the actor path from the root guardian up
|
||||
entails traversing the network, which is a costly operation. Therefore, each
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
.. _remoting:
|
||||
|
||||
Transparent Remoting
|
||||
====================
|
||||
Location Transparency
|
||||
=====================
|
||||
|
||||
The previous section describes how actor paths are used to make possible
|
||||
transparent remoting. This special feature deserves some extra explanation,
|
||||
because it is a term which was used quite differently in the context of
|
||||
programming languages, platforms and technologies.
|
||||
The previous section describes how actor paths are used to enable location
|
||||
transparency. This special feature deserves some extra explanation, because the
|
||||
related term “transparent remoting” was used quite differently in the context
|
||||
of programming languages, platforms and technologies.
|
||||
|
||||
Distributed by Default
|
||||
----------------------
|
||||
|
|
@ -60,5 +60,5 @@ to achieve this is that the developer needs to declare a certain actor as
|
|||
up a configurable number of children of the desired type and route to them in
|
||||
the configured fashion. Once such a router has been declared, its configuration
|
||||
can be freely overridden from the configuration file, including mixing it with
|
||||
the transparent remote deployment of (some of) the children. Read more about
|
||||
this in :ref:`routing`.
|
||||
the remote deployment of (some of) the children. Read more about
|
||||
this in :ref:`routing-scala` and :ref:`routing-java`.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
.. _routing-java:
|
||||
|
||||
Routing (Java)
|
||||
==============
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
.. _support:
|
||||
|
||||
`Commercial Support <http://typesafe.com>`__
|
||||
=========================================
|
||||
============================================
|
||||
|
||||
Commercial support is provided by `Typesafe <http://typesafe.com>`_.
|
||||
Akka is now part of the `Typesafe Stack <http://typesafe.com/stack>`_.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
.. _routing-scala:
|
||||
|
||||
Routing (Scala)
|
||||
===============
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue