- From: Anant Narayanan <anant@mozilla.com>
- Date: Thu, 07 Jun 2012 08:15:29 -0700
- To: SUN Yang <sun.yang.nj@gmail.com>
- CC: public-media-capture@w3.org
On 6/7/12 7:58 AM, SUN Yang wrote: > I am not sure how the resources behave when busy, but I often use chrome to test webrtc service, I often in 1 tab open a page then the page gets stream from the camera, and in another tab i open another page I can also get stream from the second page. > > And i think it will be common the same camera will be shared by different page in browser, as I always do in webrtc demo development. We can certainly implement a "development mode" where this is allowed, but in the normal-default case, I think we should enforce busy resources. If we don't it will be easy for users to forget which pages are currently using their camera and it is hard to convey the fact that the same stream is used in two different pages to the user. One concession we could make though, it to allow the same stream to be used in two different tabs but only as long as they're both from the same origin. -Anant > So I suggest we do not specify that second call to camera will counter "busy",but may promote to user that the resources currently used by which application, which has more practical meanings. > > Yang (Huawei)
Received on Thursday, 7 June 2012 15:15:56 UTC