Realtime Data API #62
Closed
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
|
has merge conflicts |
|
also CI should pass |
Septias
force-pushed
the
sk/remove_descr
branch
from
c44aa40 to
6f3b6e9
Compare
|
i want to merge the two preceding PRs first, after that I fix this PR |
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.
Add support for the webxdc spec realtime APIs. This PR got bigger than expected so I extracted some parts into separate PRs #63 #64 #65. We should merge these first so the diff of this PR gets smaller and more concise.
Status: If you create the updateListener Handler, you can send and receive realtime messages. Tested this with webxdc/ping webxdc.
Ref: https://webxdc.org/docs/spec/joinRealtimeChannel.html