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

Auto-reconnect #53

Open
dehnert opened this issue May 24, 2017 · 3 comments
Open

Auto-reconnect #53

dehnert opened this issue May 24, 2017 · 3 comments

Comments

@dehnert
Copy link
Contributor

dehnert commented May 24, 2017

AFAICT, if an exception occurs in a backend (eg, a timeout), that backend stops working. It should probably reconnect automatically, or at least have an option to do so.

@dehnert
Copy link
Contributor Author

dehnert commented May 24, 2017

Okay, it looks like Roost and IRCCloud both support explicit reconnect. It might make sense to give SnipeBackend a reconnect() method that's a no-op (assuming this isn't generalizable, which I think is likely), give the Zulip backend a useful reconnect method, and add a reconnect-all keybinding. I can work on doing that.

@kcr
Copy link
Collaborator

kcr commented May 24, 2017

yeah, an explicit reconnect function would be useful..

@dehnert
Copy link
Contributor Author

dehnert commented May 31, 2017

I can work on doing that.

I got hosed (and distracted by #55) so didn't make appreciable progress on this, unfortunately.

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

2 participants