Skip to content
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

HubConnectionManager doesn't retry to perform an initial connection when server does not exist #10

Open
dealproc opened this issue Jul 2, 2015 · 1 comment

Comments

@dealproc
Copy link

dealproc commented Jul 2, 2015

The scenario is:

SignalR Server is down for upgrade/maintenance
Client tries to connect to SignalR Server initially.

workaround:
wrap _HubConnectionManager.Initialize(); in a try...catch... block that squelches the error.

Wondering if this is the best case, or if we should squelch it within the HubConnectionManager class itself?

@dealproc
Copy link
Author

dealproc commented Sep 3, 2015

Thinking through this a bit deeper, this is a transient error in the case of HubConnectionManager. It should be logged, but the class should keep trying to connect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant