On 10/02/17 14:49, Justin Ross wrote:
On Fri, Feb 10, 2017 at 6:44 AM, Rob Godfrey <[email protected]>
wrote:
Zooming out, would it make sense to eventually introduce in AMQP an
explicit "go away, don't reconnect" variant of connection error?
What would the use case be? What would the client do in this case (go hide
in a corner / delete itself from the hard disk?). Potentially we could
augment the error with a minimum reconnect delay or something... but other
than that I think forced (reconnect according to existing policy) and
redirect (you should go somewhere else)... cover all the use cases I can
think of.
The one that springs to mind is something that is intentionally removed
from service and definitely will not return.
There are other more specialised error conditions, e.g.
amqp:resource-deleted, or maybe amqp:internal-error, that can be used to
indicate reconnect may not be of any use.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
