- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Mar 2021 14:40:50 +0000
- To: public-webrtc-logs@w3.org
Then again, I don't think it's possible to set RTOs per data channel without adding additional application-level (in this case, the WebRTC implementation) logic in order to achieve this. Min and max RTO can only be set per SCTP association while partial reliability (whether to retransmit, how often and TTL) is possible per message (WebRTC ties it to the data channel though). So, while this could be added to the spec on peer connection level, it's unlikely going to be a solution for a use case that requires different RTOs for different data channels on the same peer connection. What you can already do today though is set `maxRetransmits` to `0` and apply retransmission logic yourselves. In your use case, that might even bring the best user experience since the level of control is much higher. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2629#issuecomment-795518025 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 March 2021 14:40:55 UTC