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

Handle shaky network connectivity more resiliently #257

Open
probonopd opened this issue Nov 21, 2017 · 3 comments
Open

Handle shaky network connectivity more resiliently #257

probonopd opened this issue Nov 21, 2017 · 3 comments

Comments

@probonopd
Copy link

probonopd commented Nov 21, 2017

My reason for using this software is to be able to use IRC in situation with intermittent network connectivity, i.e., mobile, trains, etc.

When there is shaky connectivity, the web interface shows a red bar at the top (which is good).

reconnect

However, it asks me to reconnect (instead of retrying like.e.g, Gmail does) (which is slightly cumbersome), and then asks me to log in again (which is a real hassle), and shows a loading progress bar covering the entire screen (which makes it impossible to even look at the previous content).

loading

I would love to see this be optimized more for semi-online/offline use cases, since I could imagine that an IRC web client is used by more people "on the road" than just me.

@probonopd
Copy link
Author

Possibly Service Workers could be used to facilitate this.

@magne4000
Copy link
Owner

That's a really complicated problem here, that couldn't simply be solved, because it's closely tied to how current Quassel protocol works, which isn't really mobile/web friendly.
When connection is lost for any reason, we are forced to start the connection process again from the beginning.

The current reload + login part is cumbersome I agree, and this could be improved. I could just try to reconnect indefinitely without the need to refresh the page.

@probonopd
Copy link
Author

I could just try to reconnect indefinitely without the need to refresh the page.

Yes, I think this would already be a big improvement, together with a local caching of the already-downloaded queues in the browser.

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

No branches or pull requests

2 participants