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

correct small confusion (short: confuso)

Browse source
This commit is contained in:
Roland 2012-11-06 11:59:11 +01:00
parent f9eb59e883
commit ebd47bcdf6
2 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

5
akka-docs/rst/java/untyped-actors.rst
View file

@ -566,9 +566,8 @@ To hotswap the Actor using ``getContext().become``:
This variant of the :meth:`become` method is useful for many different things, This variant of the :meth:`become` method is useful for many different things,
such as to implement a Finite State Machine (FSM). It will replace the current such as to implement a Finite State Machine (FSM). It will replace the current
behavior (i.e. the top of the behavior stack), which means that behavior (i.e. the top of the behavior stack), which means that you do not use
:meth:`unbecome` is not called, instead always the next behavior is explicitly :meth:`unbecome`, instead always the next behavior is explicitly installed.
installed.
The other way of using :meth:`become` does not replace but add to the top of The other way of using :meth:`become` does not replace but add to the top of
the behavior stack. In this case care must be taken to ensure that the number the behavior stack. In this case care must be taken to ensure that the number

2
akka-docs/rst/scala/actors.rst
View file

@ -669,7 +669,7 @@ To hotswap the Actor behavior using ``become``:
This variant of the :meth:`become` method is useful for many different things, This variant of the :meth:`become` method is useful for many different things,
such as to implement a Finite State Machine (FSM, for an example see `Dining such as to implement a Finite State Machine (FSM, for an example see `Dining
Hakkers`_). It will replace the current behavior (i.e. the top of the behavior Hakkers`_). It will replace the current behavior (i.e. the top of the behavior
stack), which means that :meth:`unbecome` is not called, instead always the stack), which means that you do not use :meth:`unbecome`, instead always the
next behavior is explicitly installed. next behavior is explicitly installed.
.. _Dining Hakkers: @github@/akka-samples/akka-sample-fsm/src/main/scala/DiningHakkersOnBecome.scala .. _Dining Hakkers: @github@/akka-samples/akka-sample-fsm/src/main/scala/DiningHakkersOnBecome.scala