Last post Nov 13, 2014 03:49 PM by BrennanU
Nov 12, 2014 07:42 AM|BrennanU|LINK
Good morning all. I am working on a SignalR application whose basic principal is to subscribe to specific events on the server. Whenever one of those events fire at the server, the server calls a JS client method that does something in the browser. In my
state is not maintained.
the server on reconnect to see if the subscriptions still exist, and recreate them if not? In the second situation, can I assume that if the server disconnected event fires that that client will not reconnect without me calling connect on the client side?
Nov 12, 2014 08:28 PM|Kevin Shen - MSFT|LINK
When you stop debugging in visual studio and restart the debugging, that belongs to the Server disconnection scenarios.
When a server goes offline -- it reboots, fails, the app domain recycles, etc. -- the result might be similar to a lost connection, or the transport API and SignalR might know immediately that the server is gone, and SignalR might begin trying to reconnect
without raising the ConnectionSlow event.
If the client goes into reconnecting mode, and if the server recovers or restarts or a new server is brought online before the disconnect timeout period expires, the client will reconnect to the restored or new server.
In that case, the SignalR connection continues on the client and the Reconnected event is raised.
For more information ,I suggest that you can refer to link about Understanding and Handling Connection Lifetime Events in SignalR:
Nov 13, 2014 03:49 PM|BrennanU|LINK
Thanks Kevin, that information answers my question.