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

Make Wave more resilient to unstable networks #2252

Closed
mturoci opened this issue Feb 2, 2024 · 0 comments · Fixed by #2253
Closed

Make Wave more resilient to unstable networks #2252

mturoci opened this issue Feb 2, 2024 · 0 comments · Fixed by #2253
Assignees
Labels
feature Feature request server Related to server

Comments

@mturoci
Copy link
Collaborator

mturoci commented Feb 2, 2024

As of today, Wave requires a stable websocket connection. However, some environments cut websocket connections on purpose to save on resources which results in subpar UX.

The goal of this issue is to handle underlying reconnects in the background so that users can use the app undisturbed without notice.

  • Requires UI change to only rerender the page if reconnect failed. First reconnect should be with zero backoff (immediate).
  • Server needs to allow resumability - distinguish between reconnects and new connects.

cc @codyharris-h2o-ai @mmalohlava

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

Successfully merging a pull request may close this issue.

1 participant