Skip to content

Conversation

@achingbrain
Copy link
Member

@achingbrain achingbrain commented Nov 6, 2023

The datachannel muxer is created during set up of the Connection object. If we notify of early stream creation before the Connection object is properly configured, the early streams will be lost.

This can happen when the remote opens a data channel before the local node has finished setting up it's end of the connection.

The fix is to notify asynchronously which gives the upgrader enough time to finish setting up the Connection.

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation if necessary (this includes comments as well)
  • I have added tests that prove my fix is effective or that my feature works

The datachannel muxer is created during set up of the `Connection`
object.  If we notify of early stream connection before the
`Connection` object is properly configured, the early streams will
be lost.

The fix is to notify asynchronously which gives the upgrader enough
time to finish setting up the `Connection`.
@achingbrain achingbrain requested a review from a team as a code owner November 6, 2023 15:57
@achingbrain achingbrain changed the title fix: delay notification of early stream creation fix: delay notification of early WebRTC stream creation Nov 6, 2023
@achingbrain achingbrain merged commit d25d951 into master Nov 6, 2023
@achingbrain achingbrain deleted the fix/delay-early-stream-notification branch November 6, 2023 17:39
This was referenced Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants