Connection stalled

[baalbaki]

Hi Giuseppe, yes its plausible that the client app gets stuck in some way delaying the handling of those events.
What can happen if in my client if onUnsubscrAll events are not called yet and I connect to another source, then the callbacks are received later:
1-Will I receive values from the old source?
2-Will the new source still be connected properly?
3-If after I received all those callbacks, will we get all the new values from the new source normally?
Thanks

[giuseppe.corti]

Hi baalbaki,

It is not very clear to me when you say "if in my client if onUnsubscrAll events are not called yet and I connect to another source":
did you mean that your client received the onFailure event con the connection but not the onUnsubscrAll events?
Or the client does not receive the onFailure event and nor the onUnsubscrAll events.
Indeed in this latter case it could be that the client library does not detect the failure of the connection with the server and would therefore be waiting for the timeouts.

Specifically for your questions:

1. yes there might be the possibility to receive some further onUpdate call.
2. - 3. About the new connection you should rely on the onSessionStarted event after which you can be confident of a fully active client session with the server (regardless of the situation of any old sessions.).

That said, I would like to ask if you have the chance to upgrade the client library to the latest available version.
I am aware that the API has changed radically, and therefore would require some effort in updating the client code; but please note that the version in use is now very old and out of support.
You will also benefit from new features (as the websocket transport), enhancements and bug fixes introduced in the years.

Regards,
Giuseppe