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

=doc Remoting documentation addition (#20463) (#20584)

Browse source 
* Add missing fullstop

* Document that sends to local actors via remote paths aren't remoted (#20463)
This commit is contained in:
David Piggott 2016-05-24 10:21:03 +01:00 • committed by Konrad Malawski
parent 11584f12eb
commit dfc7943e94
2 changed files with 25 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

15
akka-docs/rst/java/remoting.rst
View file

@ -88,6 +88,17 @@ the :class:`ActorSelection`, which returns a ``Future`` of the matching
For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`. For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`.
.. note::
Message sends to actors that are actually in the sending actor system do not
get delivered via the remote actor ref provider. They're delivered directly,
by the local actor ref provider.
Aside from providing better performance, this also means that if the hostname
you configure remoting to listen as cannot actually be resolved from within
the very same actor system, such messages will (perhaps counterintuitively)
be delivered just fine.
Creating Actors Remotely Creating Actors Remotely
^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^
@ -247,7 +258,7 @@ Serialization
When using remoting for actors you must ensure that the ``props`` and ``messages`` used for When using remoting for actors you must ensure that the ``props`` and ``messages`` used for
those actors are serializable. Failing to do so will cause the system to behave in an unintended way. those actors are serializable. Failing to do so will cause the system to behave in an unintended way.
For more information please see :ref:`serialization-java` For more information please see :ref:`serialization-java`.
Routers with Remote Destinations Routers with Remote Destinations
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -495,4 +506,4 @@ special configuration that sets both the logical and the bind pairs for remoting
bind-port = 2552 # internal (bind) port bind-port = 2552 # internal (bind) port
} }
} }
} }

13
akka-docs/rst/scala/remoting.rst
View file

@ -94,6 +94,17 @@ the :class:`ActorSelection`, which returns a ``Future`` of the matching
For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`. For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`.
.. note::
Message sends to actors that are actually in the sending actor system do not
get delivered via the remote actor ref provider. They're delivered directly,
by the local actor ref provider.
Aside from providing better performance, this also means that if the hostname
you configure remoting to listen as cannot actually be resolved from within
the very same actor system, such messages will (perhaps counterintuitively)
be delivered just fine.
Creating Actors Remotely Creating Actors Remotely
^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^
@ -252,7 +263,7 @@ Serialization
When using remoting for actors you must ensure that the ``props`` and ``messages`` used for When using remoting for actors you must ensure that the ``props`` and ``messages`` used for
those actors are serializable. Failing to do so will cause the system to behave in an unintended way. those actors are serializable. Failing to do so will cause the system to behave in an unintended way.
For more information please see :ref:`serialization-scala` For more information please see :ref:`serialization-scala`.
Routers with Remote Destinations Routers with Remote Destinations
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^