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

Doc changes after review of PR 724

Browse source
This commit is contained in:
Viktor Klang 2012-09-21 12:00:35 +02:00
parent 542b927bdb
commit 412f84b6f3
3 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
akka-docs/general/message-send-semantics.rst
View file

@ -104,8 +104,8 @@ Dead Letters Which are (Usually) not Worrisome
---------------------------------------------- ----------------------------------------------
Every time an actor does not terminate by its own decision, there is a chance Every time an actor does not terminate by its own decision, there is a chance
that some messages are lost which it sends to itself. There is one which may that some messages which it sends to itself are lost. There is one which
happen in complex shutdown scenarios quite easily which is usually benign: happens quite easily in complex shutdown scenarios that is usually benign:
seeing a :class:`akka.dispatch.Terminate` message dropped means that two seeing a :class:`akka.dispatch.Terminate` message dropped means that two
termination requests were given, but of course only one can succeed. In the termination requests were given, but of course only one can succeed. In the
same vein, you might see :class:`akka.actor.Terminated` messages from children same vein, you might see :class:`akka.actor.Terminated` messages from children

2
akka-docs/general/supervision.rst
View file

@ -148,7 +148,7 @@ The precise sequence of events during a restart is the following:
#. wait for all children which were requested to terminate (using #. wait for all children which were requested to terminate (using
``context.stop()``) during :meth:`preRestart` to actually terminate ``context.stop()``) during :meth:`preRestart` to actually terminate
#. create new actor instance by invoking the originally provided factory again #. create new actor instance by invoking the originally provided factory again
#. invoke :meth:`postRestart` on the new instance #. invoke :meth:`postRestart` on the new instance (which by default also calls :meth:`preStart`)
#. send restart request to all children (they will follow the same process #. send restart request to all children (they will follow the same process
recursively, from step 2) recursively, from step 2)
#. resume the actor #. resume the actor

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

@ -126,6 +126,10 @@ As you can see from the example above the following pattern is used to find an `
but send ``Props`` to a remotely looked-up actor and have that create a but send ``Props`` to a remotely looked-up actor and have that create a
child, returning the resulting actor reference. child, returning the resulting actor reference.
.. warning::
*Caveat:* Akka Remoting does not trigger Death Watch for lost connections.
Programmatic Remote Deployment Programmatic Remote Deployment
------------------------------ ------------------------------