deprecate ReliableProxy, #22198
This commit is contained in:
parent
25385e15f2
commit
77b1e87c12
3 changed files with 13 additions and 0 deletions
|
|
@ -3,6 +3,10 @@
|
|||
Reliable Proxy Pattern
|
||||
======================
|
||||
|
||||
.. warning::
|
||||
**Deprecation warning** - ``ReliableProxy`` has been deprecated and is scheduled for removal
|
||||
in the next major version. Use :ref:`at-least-once-delivery-scala` instead.
|
||||
|
||||
Looking at :ref:`message-delivery-reliability` one might come to the conclusion that
|
||||
Akka actors are made for blue-sky scenarios: sending messages is the only way
|
||||
for actors to communicate, and then that is not even guaranteed to work. Is the
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ import scala.concurrent.duration._
|
|||
import scala.util.Try
|
||||
import java.util.concurrent.TimeUnit
|
||||
|
||||
@deprecated("Use AtLeastOnceDelivery instead", "2.5.0")
|
||||
object ReliableProxy {
|
||||
/**
|
||||
* Scala API Props. Arguments are detailed in the [[akka.contrib.pattern.ReliableProxy]]
|
||||
|
|
@ -224,6 +225,7 @@ import ReliableProxy._
|
|||
* @param maxConnectAttempts is an optional maximum number of attempts to connect to the
|
||||
* target actor. Use `None` for no limit. If `reconnectAfter` is `None` this value is ignored.
|
||||
*/
|
||||
@deprecated("Use AtLeastOnceDelivery instead", "2.5.0")
|
||||
class ReliableProxy(targetPath: ActorPath, retryAfter: FiniteDuration,
|
||||
reconnectAfter: Option[FiniteDuration], maxConnectAttempts: Option[Int])
|
||||
extends Actor with LoggingFSM[State, Vector[Message]] with ReliableProxyDebugLogging {
|
||||
|
|
|
|||
|
|
@ -577,6 +577,13 @@ PeekMailbox
|
|||
|
||||
.. _migration-guide-TimerBasedThrottler:
|
||||
|
||||
ReliableProxy
|
||||
-------------
|
||||
|
||||
``ReliableProxy`` is deprecated. Use :ref:`at-least-once-delivery-scala` instead. ``ReliableProxy``
|
||||
was only intended as an example and doesn't have full production quality. If there is demand
|
||||
for a lightweight (non-durable) at-least once delivery mechanism we are open for a design discussion.
|
||||
|
||||
TimerBasedThrottler
|
||||
-------------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue