- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Oct 2017 21:01:05 +0000
- To: public-webrtc-logs@w3.org
Thanks for the pointer to the native API, that does solve an issue. However, having this baked into the JS API would make the feature available universally. Furthermore, the fact that it is useful for the native bindings further endorses this point. I could live with this being an initial estimate for all the streams carried over the peerconnection. RTCConfig sounds reasonable. About it being in v1.0, I am not very particular about it, although it seems straightforward to surface an existing feature with simple semantics. @taylor-b was that a naming thing or did it not make sense to put it in there? -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1635#issuecomment-336566252 using your GitHub account
Received on Friday, 13 October 2017 21:00:54 UTC