-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconnecting question #118
Comments
Not sure if this helps but we've implemented a custom retry. This is over simplified but basically, we listen for connection status, on error we delay, and then call connection start again. This allows us to create any retry logic we want. |
Our solution was very similar to your solution. I just asked if there is any built-in option which was forgotten from the wiki |
Hi, I am sorry to ask but I would like to know if this would be something like this:
I |
Sorry, I don't remember our solution, it's a really old thread. This solution what you wrote could work. |
yes works fine but uses the another signalr connection id while establishing new connection |
I have 2 questions regarding reconnect
If the first connect fails, no more reconnects are made automatically. Can we enable auto reconnect on connect failure?
If the connection interrupts, the client will try for 10 times to reconnect. If even the last reconnect fails, the state sets to disconnect and doesn't try to reconnect any more. Is there any possibility to set this limit to infinite?
The text was updated successfully, but these errors were encountered: