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

=per Fix minor doc issues

Browse source 
(cherry picked from commit 45c07e1f2f131e70a03b82803f11fd390572ccba)
This commit is contained in:
Patrik Nordwall 2014-06-28 17:32:03 +02:00
parent bc2aeaf0d3
commit 9a4425ed19
4 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
akka-docs/rst/java/lambda-persistence.rst
View file

@ -413,7 +413,7 @@ sequence number. It does not store this state itself. You must persist events co
``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can ``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can
be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes
these events can be derived from other business level events, and sometimes you must create separate events. these events can be derived from other business level events, and sometimes you must create separate events.
During recovery calls to ``delivery`` will not send out the message, but it will be sent later During recovery calls to ``deliver`` will not send out the message, but it will be sent later
if no matching ``confirmDelivery`` was performed. if no matching ``confirmDelivery`` was performed.
Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``. Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``.

2
akka-docs/rst/java/persistence.rst
View file

@ -419,7 +419,7 @@ sequence number. It does not store this state itself. You must persist events co
``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can ``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can
be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes
these events can be derived from other business level events, and sometimes you must create separate events. these events can be derived from other business level events, and sometimes you must create separate events.
During recovery calls to ``delivery`` will not send out the message, but it will be sent later During recovery calls to ``deliver`` will not send out the message, but it will be sent later
if no matching ``confirmDelivery`` was performed. if no matching ``confirmDelivery`` was performed.
Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``. Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``.

4
akka-docs/rst/scala/persistence.rst
View file

@ -376,7 +376,7 @@ use the ``deleteSnapshots`` method.
At-Least-Once Delivery At-Least-Once Delivery
====================== ======================
To send messages with at-least-once delivery semantics to destinations you can add the ``AtLeastOnceDelivery`` To send messages with at-least-once delivery semantics to destinations you can mix-in ``AtLeastOnceDelivery``
trait to your ``PersistentActor`` on the sending side. It takes care of re-sending messages when they trait to your ``PersistentActor`` on the sending side. It takes care of re-sending messages when they
have not been confirmed within a configurable timeout. have not been confirmed within a configurable timeout.
@ -417,7 +417,7 @@ sequence number. It does not store this state itself. You must persist events co
``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can ``deliver`` and ``confirmDelivery`` invocations from your ``PersistentActor`` so that the state can
be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes be restored by calling the same methods during the recovery phase of the ``PersistentActor``. Sometimes
these events can be derived from other business level events, and sometimes you must create separate events. these events can be derived from other business level events, and sometimes you must create separate events.
During recovery calls to ``delivery`` will not send out the message, but it will be sent later During recovery calls to ``deliver`` will not send out the message, but it will be sent later
if no matching ``confirmDelivery`` was performed. if no matching ``confirmDelivery`` was performed.
Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``. Support for snapshots is provided by ``getDeliverySnapshot`` and ``setDeliverySnapshot``.

4
akka-persistence/src/main/scala/akka/persistence/AtLeastOnceDelivery.scala
View file

@ -71,7 +71,7 @@ object AtLeastOnceDelivery {
} }
/** /**
* Use this trait with your `PersistentActor` to send messages with at-least-once * Mix-in this trait with your `PersistentActor` to send messages with at-least-once
* delivery semantics to destinations. It takes care of re-sending messages when they * delivery semantics to destinations. It takes care of re-sending messages when they
* have not been confirmed within a configurable timeout. Use the [[#deliver]] method to * have not been confirmed within a configurable timeout. Use the [[#deliver]] method to
* send a message to a destination. Call the [[#confirmDelivery]] method when the destination * send a message to a destination. Call the [[#confirmDelivery]] method when the destination
@ -90,7 +90,7 @@ object AtLeastOnceDelivery {
* to the `deliver` and `confirmDelivery` invocations from your `PersistentActor` so that the * to the `deliver` and `confirmDelivery` invocations from your `PersistentActor` so that the
* state can be restored by calling the same methods during the recovery phase of the * state can be restored by calling the same methods during the recovery phase of the
* `PersistentActor`. Sometimes these events can be derived from other business level events, * `PersistentActor`. Sometimes these events can be derived from other business level events,
* and sometimes you must create separate events. During recovery calls to `delivery` * and sometimes you must create separate events. During recovery calls to `deliver`
* will not send out the message, but it will be sent later if no matching `confirmDelivery` * will not send out the message, but it will be sent later if no matching `confirmDelivery`
* was performed. * was performed.
* *