feat: add asynchronous sendAsync to RTCDataChannel - #246
Merged
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
2 participants
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.
send marshals to the signaling thread and blocks the caller until the engine has taken the payload, so applications pushing high message rates over many channels pay a synchronous round trip per message.
sendAsync forwards to the engine's asynchronous send path. The payload window (position to limit) is copied on the native side before the call returns, so the Java buffer can be reused immediately. Errors are reported asynchronously: queueing failures are logged natively, and fatal errors close the data channel, which the registered RTCDataChannelObserver sees as a state change. Existing send is unchanged.