Disconnect / Reconnect

[aswanevelder]

Hi guys,

Are there javascript events available yet for Disconnect and Reconnect as was available in SignalR 2?

Thanks

[austinfelipe]

@aswanevelder I don't think so, at least I couldn't find it. I'm doing it using onclose event and just creating a brand new HubConnection 🤔

[moozzyk]

There is no reconnect in this version of SignalR so there is no event. onclose is called when the connection is closed.
You can now use websockets to connect to SignalR (i.e. no client is needed) - here is an example (which I need to finish and merge but it should give you an idea)

[davidfowl]

We're looking at adding the automatic reconnect functionality back to SignalR in the next preview release.

[aswanevelder]

Thanks guys, @davidfowl looking forward to it!

[KirilRusev]

@davidfowl sounds great! Do you have road map for the next few months?

[AwsomeCode]

@davidfowl @aswanevelder @KirilRusev
Please don't add reconnect. Its kind of confusing to manage. If client get disconnected, client can initiate reconnect. Its better that server should not manage reconnects.

[davidfowl]

It’s all client side. All we’re going to do is make sure the connection is reusable and there’s a way to auto reconnect. The server isn’t managing anything

[analogrelay]

Restarting the connection is now supported in the .NET client (in PR #1147).

#1171 is tracking adding support to the TypeScript client.

Given that, I'm going to close this issue. Feel free to comment if you still have concerns!

[BrennanConroy]

Reopening, we are going to be adding automatic reconnect

Closed event called once reconnect tries are done
Need to decide on number of reconnect tries
Add configurability
Back-off delay between reconnect tries
StopAsync stops reconnect
Keep connection re-usability