* Add missing fullstop * Document that sends to local actors via remote paths aren't remoted (#20463)
This commit is contained in:
parent
11584f12eb
commit
dfc7943e94
2 changed files with 25 additions and 3 deletions
|
|
@ -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`.
|
||||
|
||||
.. 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
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
|
@ -252,7 +263,7 @@ Serialization
|
|||
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.
|
||||
|
||||
For more information please see :ref:`serialization-scala`
|
||||
For more information please see :ref:`serialization-scala`.
|
||||
|
||||
Routers with Remote Destinations
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue