transparent remoting -> location transparency

This commit is contained in:
Roland 2011-12-15 19:02:47 +01:00
parent 987a8cc2ee
commit fd4b4e3fb3
5 changed files with 14 additions and 10 deletions

View file

@ -100,7 +100,7 @@ Physical Actor Paths
^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^
While the logical actor path describes the functional location within one actor 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 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 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 entails traversing the network, which is a costly operation. Therefore, each

View file

@ -1,12 +1,12 @@
.. _remoting: .. _remoting:
Transparent Remoting Location Transparency
==================== =====================
The previous section describes how actor paths are used to make possible The previous section describes how actor paths are used to enable location
transparent remoting. This special feature deserves some extra explanation, transparency. This special feature deserves some extra explanation, because the
because it is a term which was used quite differently in the context of related term “transparent remoting” was used quite differently in the context
programming languages, platforms and technologies. of programming languages, platforms and technologies.
Distributed by Default 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 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 the configured fashion. Once such a router has been declared, its configuration
can be freely overridden from the configuration file, including mixing it with can be freely overridden from the configuration file, including mixing it with
the transparent remote deployment of (some of) the children. Read more about the remote deployment of (some of) the children. Read more about
this in :ref:`routing`. this in :ref:`routing-scala` and :ref:`routing-java`.

View file

@ -1,3 +1,5 @@
.. _routing-java:
Routing (Java) Routing (Java)
============== ==============

View file

@ -1,7 +1,7 @@
.. _support: .. _support:
`Commercial Support <http://typesafe.com>`__ `Commercial Support <http://typesafe.com>`__
========================================= ============================================
Commercial support is provided by `Typesafe <http://typesafe.com>`_. Commercial support is provided by `Typesafe <http://typesafe.com>`_.
Akka is now part of the `Typesafe Stack <http://typesafe.com/stack>`_. Akka is now part of the `Typesafe Stack <http://typesafe.com/stack>`_.

View file

@ -1,3 +1,5 @@
.. _routing-scala:
Routing (Scala) Routing (Scala)
=============== ===============