Add WebRTC IO support - #99
Open
mirsella wants to merge 3 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hello !
Closes #98
Adds
aeronet_webrtc, with native client/server support and browser client support. WebRTC signaling is kept separate from the IO layer and routed through an application-provided signaling service.Each session uses one unordered, unreliable binary
DataChannelwith a 1000-byte MTU. Reliability, ordering, and fragmentation remain inaeronet_transport.Added lines by category:
Cargo.lock: 1,032Tested with native and WASM checks, headless Chromium, direct connections, and TURN over UDP, TCP, and TLS.
Publishing requires releasing
aeronet_tokio_runtimefirst.No problem if this is not an implementation or direction you want for Aeronet. Feel free to close the PR.