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

Disconnect old websockets #4953

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

masenf
Copy link
Collaborator

@masenf masenf commented Mar 12, 2025

Disconnect websockets more aggressively

  • page beforeunload and unload
  • when a new event comes in for the same token with a different sid

masenf added 2 commits March 12, 2025 06:59
When an event is received that will associate a client token with a new sid,
disconnect the previous sid, since it will no longer be used.
Copy link

codspeed-hq bot commented Mar 12, 2025

CodSpeed Performance Report

Merging #4953 will not alter performance

Comparing masenf/disconnect-old-websockets (5d1d66c) with main (c472990)

Summary

✅ 12 untouched benchmarks

@Lendemor
Copy link
Collaborator

Related to #4607 I think.

Disconnecting on new sid for same token means the original page will get disconnected?

@masenf
Copy link
Collaborator Author

masenf commented Mar 12, 2025

Disconnecting on new sid for same token means the original page will get disconnected?

yes; this is intended to handle the case where page is refreshed (in an iframe) or hot reloaded and ends up with a new websocket, but never closes out the old one.

that said, i think the frontend logic might be good enough, and i wasn't actually able to hit that log message during actual testing.

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

Successfully merging this pull request may close these issues.

2 participants