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.

Sign up for GitHub

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

Jump to bottom

Handle disconnecting of websocket #3

Open

relrod opened this issue Nov 5, 2014 · 0 comments

Milestone

Member

relrod commented Nov 5, 2014

If we lose the connection we should either:

Inform the user, attempt to autoreconnect
Or, at minimum, inform the user, tell them to try refreshing.

Option 2 is more appealing in the short term, since I want to feature-freeze for NBP1 on November 8th (3 days from this writing).

relrod modified the milestone: v2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment