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

Use Redis for Socket.IO sessions, instead of Socket.IO sessions #387

Open
mawoka-myblock opened this issue Jul 10, 2024 · 1 comment
Open
Assignees
Labels
complexity:2 enhancement New feature or request prio:2 Medium priority

Comments

@mawoka-myblock
Copy link
Owner

This would dramatically improve reliability.

Requirement: Unique ID for every browser, decoupled from the Socket.IO id. Maybe generated on join and put into the URL or localStorage to survive a page reload reliably

@mawoka-myblock mawoka-myblock added enhancement New feature or request prio:2 Medium priority complexity:2 labels Jul 10, 2024
@mawoka-myblock mawoka-myblock self-assigned this Jul 11, 2024
@mawoka-myblock
Copy link
Owner Author

Okay, this is basically done, BUT there are mentions throughout the whole part where the sid is used for different purposes, should not be done like that if possible to achieve the long-term goal of surviving network interruptions and page reloads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:2 enhancement New feature or request prio:2 Medium priority
Projects
None yet
Development

No branches or pull requests

1 participant