Documentation mentions requirement to resubscribe upon reconnection

[Craig-J]

Last paragraph here mentions:

Beware that you need to resubscribe to channels after reconnection happens. You should subscribe to ReconnectionHappened stream and send subscription requests.

In my experience this seems to be untrue - I am continuing to get events from all of ReconnectionHappened, DisconnectionHappened and MessageReceived after a reconnection. Am I misunderstanding the situation where you must subscribe again or are the docs wrong?

If required to answer you can see the code I've written here.

[jjxtra]

Seems like docs are wrong, in either case having to resubscribe seems like an error in architecture, since the inner socket is being handled separately, the subscribe is an abstraction over the background processing/handling of the web socket.

[Marfusios]

Sorry, the documentation is a little misleading.
By "channels" here, we mean subscriptions/groups on the server side.
Every websocket server solves it differently.

So inside ReconnectionHappened stream, you should send requests again, e.g.:

client.ReconnectionHappened.Subscribe(info =>
    {
         client.Send("{ type: subscribe, kind: something}"); // json/text, whatever the server expects
    });