- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Mar 2019 00:55:54 +0000
- To: public-webrtc-logs@w3.org
I agree with @jan-ivar and would vote for B. Option A requires a comprehensive list of use cases to properly design things, maybe it should be in scope of WebRTC NV. I can see some usecases. For local tracks, a browser might be able to support capture of two cameras at the same time, but not three. If one website is already capturing with 1 cameras, a second website might be able to do getUserMedia for 1 camera but not 2. It is unclear what kind of information should be given to the application so that it can take appropriate measures, whether the current OverconstrainedError is a good fit there, what the privacy implications are... For remote tracks, I can see a case where a user agent may hit a decoder slot limitation, which is a resource shared amongst different applications. In this particular case, the straightforward option would be to have something on receiver side, not on the track. Again, not sure which kind of information should be given to the application. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/573#issuecomment-473119986 using your GitHub account
Received on Friday, 15 March 2019 00:55:55 UTC