Automatic Reconnect
When a temporary network outage disconnects an eFTL client from the eFTL service, the client library automatically attempts to reconnect to the eFTL service.
This feature is transparent to the client application and to the developer.
During the disconnect, the client library buffers messages that the application publishes. Upon reconnect, the client library transmits those messages to the eFTL service.
Similarly, during the disconnect, the eFTL service buffers outbound messages to the client’s subscribers. Upon reconnect, the eFTL service transmits those messages.
Reconnection attempts continue until the client call exceeds its value of the limiting parameter on auto-reconnect attempts. If the connect call does not supply a value for maximum attempts, the default behavior makes five reconnect attempts.
With each subsequent reconnection attempt the time interval to the next attempt doubles until it would exceed the value of the limiting parameter auto-reconnect maximum delay, after which it remains at that maximum delay value. If the connect call does not supply a value for maximum delay, the default value is 30 seconds.
If automatic reconnect fails, then both client and eFTL service discard buffered messages, and the application’s disconnect callback determines its response to the longer network outage.