feat: use websockets to update info on pages #33
Conversation
This file contains 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
|
Oh thank you! I actually had websockets in mind once I realized gRPC was silly for this. |
5HT2
added
enhancement
|
great, thanks! |
lmaotrigine
force-pushed
the
feature/websockets
branch
from
14f2c9d
to
49172cf
Compare
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.
Fixes #23
Well, sort of. This currently does what I do in my rewrite (just send the JSON every second). Ideally, I'm thinking this should only send messages when the stats actually update, but then the interactive update of the relative times should be handled client-side, just like earlier so I'm undecided on whether to implement that or not.
In either case, this is an improvement over making an API request every second.