Websocket behavior in case of connection issues

[gitmalong]

Hi!

Does the Websocket client automatically reestablish terminated connections and re-subscribe or is that something I have to implement on top? If the latter is true what would be a good starting point?

I basically want to ensure that the connection is active whenever possible and don't loose any subscriptions.

Thanks for these insights.

[niklasad1]

Hey @gitmalong,

Does the Websocket client automatically reestablish terminated connections and re-subscribe or is that something I have to implement on top?

No, that's something you have to implement yourself. We had some discussions about in the past see #236 for further info.

I basically want to ensure that the connection is active whenever possible and don't loose any subscriptions.

You have to check that yourself by either Client::is_closed or if any call returns Error::RestartNeeded. The subscription itself "should" return None if the connection is closed or subscription is dropped but keep in mind that messages will buffered up to max_notifs_per_subscriptions and those will available even if the connection gets closed. In other words you would have drain all messages to get to that point. Thus, you should be able to ensure that no messages are lost (as long your buffers are large enough) but might be gaps if your connection gets closed.

However, one improvement could be get a callback via future or something to triggers once connection is closed.
You simply have to drop the client and create a new one.

[niklasad1]

Closing this because I answered your question, re-open again if something wasn't not clear in my answer.