Closed CouleeApps closed 8 months ago
This seems like a webrtc issue that will solve itself with time. Just needs more attention on the webrtc side. It seems there's 0 urgency on it, because no one is pointing out the issue in a pull request or a minimum reproducible example.
I'm not satisfied relying on or working around it. If you want to do that in your own code, you may.
Closing because it's not our bug
Due to https://github.com/webrtc-rs/webrtc/issues/371, trying to construct a data channel with
RTCDataChannelInit::max_retransmits: Some(0)
will actually produce a reliable (though unordered?) channel. After a bit of testing on my own, I found that even under significant packet loss, all packets sent on the unreliable channel still arrive and perfectly in order. I tried playing around with the parameters toRTCDataChannelInit
and have not found a configuration yet that actually produces an unreliable channel.With that being said, I guess the issue in this repo mostly revolves around:
I'm not sure what you want to do / what is even actionable from this, but it is still a downstream problem in this crate.
Reference for things I tried:
max_retransmits
to 1 instead of 0max_packet_life_time
as 1 (ms) instead of NonePartialReliableRexmitUnordered
orPartialReliableTimedUnordered
based on the provided configs