You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for input on what happens after a disconnect (not just connection interruption, but after the DisconnectTimeout period ends and the client disconnects).
According to ASP.NET documentation, all Group subscriptions are lost after a disconnect. Just looking for input on what the best course of action should be on the part of the HubConnectionManager after this happens.
Should it facilitate re-subscribing to those groups after connection is re-established?
Currently, I am doing this manually on the client by subscribing to the StateChanged event and calling a method on the Hub that subscribes again to the appropriate groups.
The text was updated successfully, but these errors were encountered:
If there's a way to encapsulate the re-subscription to the groups, then it makes sense to extend the code base for this. After all, the point of this is to "manage" the signalr connection.
Looking for input on what happens after a disconnect (not just connection interruption, but after the DisconnectTimeout period ends and the client disconnects).
According to ASP.NET documentation, all Group subscriptions are lost after a disconnect. Just looking for input on what the best course of action should be on the part of the HubConnectionManager after this happens.
Should it facilitate re-subscribing to those groups after connection is re-established?
Currently, I am doing this manually on the client by subscribing to the
StateChanged
event and calling a method on the Hub that subscribes again to the appropriate groups.The text was updated successfully, but these errors were encountered: