Adding webrtc-aside. #104
Open
Adding webrtc-aside. #104
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
This transport is yet an other webrtc transport but instead of current it doesn't use any meeting server or any protocol. Instead it use a libp2p stream so it can use circuit or ws for SDP trickle exchange. The only drawback is it require routing. Then its DTLS for security and SCTP for muxing.
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 transport is yet an other webrtc transport but instead of current it doesn't use any meeting server.
Instead it use a libp2p stream so it can use circuit or ws for SDP trickle exchange.
The only drawback is it require routing.
Then its DTLS for security and SCTP for muxing (avoiding 2 layer of encryption (the one of webrtc and secio or tls)).