- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jun 2024 07:58:48 +0000
- To: public-webrtc-logs@w3.org
I also opened #55 for stats so JS can observe these drops. I'm not that sure whether JS would actually need to control the max length of these queues tbh - it might know how often it's going to read, and the likely packet frequency coming, but the other side of the tradeoff is just memory consumption - wouldn't the browser be best placed to evaluate that tradeoff? Any extra knowledge the app would have that I've missed? Maybe just exposing readonly `incomingMaxAge` and `outgoingMaxAge` decided by the browser would be enough, so JS knows how often to query to ensure no data is lost? CC those who commented on the review on #42: @aboba @Philipel-WebRTC @youennf @pthatcher -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/54#issuecomment-2180053875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 June 2024 07:58:48 UTC