-
-
Notifications
You must be signed in to change notification settings - Fork 981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Unreliable DataChannels #57
Comments
reading through the source a bit more, seems like the data channel and the peer are closely coupled |
There's already an issue open for supporting creating additional data channels: #19 For starters, we could support unreliable data channels. |
cool - i'll close this as a duplicate |
So you don't need unreliable channels? |
I do, but I feel like this issue falls cleanly under #19. I think you already support unreliable data channels via setting |
Yep, that's right. |
I'm looking to use webRTC to create a pair of RTCDataChannels per peer:
{ reliable: true, ordered: true }
transport{ reliable: false, ordered: false }
transportThis may be out of the scope of
simple-peer
but is there a simple way of creating additional dataChannels for a peer?The text was updated successfully, but these errors were encountered: