Store maybe-missed socket messages in SQLite #727
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Broadcast messages are only stored once, not duplicated for each 'lost connection' - In the future, reconnections will be able to specify the last event ID that was observed by the client instead of having the server make assumptions - In the future, this could be used to show some chat backscroll when users join..?
goto-bus-stop
commented
Dec 12, 2025
| .execute(); | ||
| disconnectedUsers.forEach((user) => { | ||
| this.add(this.createLostConnection(user, 'TODO: Actual session ID!!')); | ||
| this.add(this.createLostConnection(user, 'TODO: Actual session ID!!', null)); |
Member
Author
There was a problem hiding this comment.
might be a good time to solve this now(?)
Member
Author
There was a problem hiding this comment.
No it's not 😇
I think when all session state is in SQLite this will be feasible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
connection'
that was observed by the client instead of having the server make
assumptions
users join..?