- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Mar 2019 20:40:36 +0000
- To: public-webrtc-logs@w3.org
This sounds like an interesting new feature, but a new feature nonetheless. I worry it's a bit late to be considering new features in 1.0. New features take time, and we've mostly been focused on finishing 1.0 over the last year, which I think means saying no to new features at this point. I also have some concerns with this API. It's essentially an API for JS to make browsers stutter. How web compatible is it to outsource control of our jitter buffer length? As a non-dominant vendor, we sometimes see web sites not testing their site with every browser or platform, so giving this tuning control to someone who may never test its effect on our browser, isn't terribly appealing. When things stutter people blame the browser. I'm not immune to its benefits, just making a point that it might take a while to work out the details, which might be better done in an extension spec? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2138#issuecomment-475774761 using your GitHub account
Received on Friday, 22 March 2019 20:40:38 UTC