Current behavior
When establishing a peer to peer connection with RTCDataChannel, Netflux delegates RTCDataChannel options negotiation to the WebRTC API.
Expected behavior
Use out-of-band negotiation of channel parameters when establishing an RTCDataChannel.
What is the motivation / use case for changing the behavior?
In practice, there are no additional performance benefits to using out-of-band negotiation with few participating peers. However, where this workflow can be useful is in cases with many participating peers, as a full-mesh network for example.
Current behavior When establishing a peer to peer connection with RTCDataChannel, Netflux delegates RTCDataChannel options negotiation to the WebRTC API.
Expected behavior Use out-of-band negotiation of channel parameters when establishing an RTCDataChannel.
What is the motivation / use case for changing the behavior? In practice, there are no additional performance benefits to using out-of-band negotiation with few participating peers. However, where this workflow can be useful is in cases with many participating peers, as a full-mesh network for example.