Node.js client #9
Open
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
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.
This PR adds a client targeted to be used in Node.js apps, so they can act as clients of the signaling server and participants of the mesh network, for example to implement a proxy to send streams to an MCU or SFU. It has been done by reverse-engineering the protocol from the actual signaling server implementation.
Additionally, it does some improvements in the project and code structure, like unifying the place where messages are decoded, and some backward compatible improvements and fixes in the protocol itself, like ensure that all request messages generate an answer that clients can wait for.
This work has been sponsored by Atos Research & Innovation, with funds from European Union H2020 program.