- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Oct 2017 21:01:35 +0000
- To: public-webrtc-logs@w3.org
This is a use case we've run into as well. Also, sometimes the application may have more knowledge about the network than the browser does, and has a better idea of what bandwidth it's capable of supporting. We added a [native-only API](https://cs.chromium.org/chromium/src/third_party/webrtc/api/peerconnectioninterface.h?q=peerconnectioninterface&dr=CSs&l=786) for this kind of use case. I think the only question is whether this is in scope for WebRTC 1.0. This also may be slightly related: https://github.com/w3c/ortc/issues/603 -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1635#issuecomment-336265996 using your GitHub account
Received on Thursday, 12 October 2017 21:01:22 UTC