=doc: Document that EventBus do not preserve sender #2918

This commit is contained in:
Endre Sándor Varga 2013-07-02 12:11:50 +02:00
parent 1cca2b85e3
commit 7dba4435e4
2 changed files with 12 additions and 0 deletions

View file

@ -21,6 +21,12 @@ implementing a simple interface:
according to the specific bus (see `Classifiers`_) and then published to all according to the specific bus (see `Classifiers`_) and then published to all
subscribers for the obtained classifier subscribers for the obtained classifier
.. note::
Please note that the EventBus does not preserve the sender of the
published messages. If you need a reference to the original sender
you have to provide it inside the message.
This mechanism is used in different places within Akka, e.g. the This mechanism is used in different places within Akka, e.g. the
:ref:`DeathWatch <deathwatch-java>` and the `Event Stream`_. Implementations :ref:`DeathWatch <deathwatch-java>` and the `Event Stream`_. Implementations
can make use of the specific building blocks presented below. can make use of the specific building blocks presented below.

View file

@ -22,6 +22,12 @@ implementing a simple interface:
according to the specific bus (see `Classifiers`_) and then published to all according to the specific bus (see `Classifiers`_) and then published to all
subscribers for the obtained classifier subscribers for the obtained classifier
.. note::
Please note that the EventBus does not preserve the sender of the
published messages. If you need a reference to the original sender
you have to provide it inside the message.
This mechanism is used in different places within Akka, e.g. the This mechanism is used in different places within Akka, e.g. the
:ref:`DeathWatch <deathwatch-scala>` and the `Event Stream`_. Implementations :ref:`DeathWatch <deathwatch-scala>` and the `Event Stream`_. Implementations
can make use of the specific building blocks presented below. can make use of the specific building blocks presented below.