- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 8 Jul 2015 09:14:08 +1000
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: public-media-capture@w3.org, Jan-Ivar Bruaroey <jib@mozilla.com>
- Message-ID: <CAHp8n2mUXGs37LPqbH=nWP+CZQ9aTfHpGz3sSH-nTb3VSOARWw@mail.gmail.com>
On 8 Jul 2015 8:00 am, "Harald Alvestrand" <harald@alvestrand.no> wrote: > > Den 07. juli 2015 23:06, skrev Silvia Pfeiffer: > > > > On 7 Jul 2015 6:52 am, "Jan-Ivar Bruaroey" <jib@mozilla.com > > <mailto:jib@mozilla.com>> wrote: > >> > >> On 7/6/15 4:00 PM, Harald Alvestrand wrote: > >>> > >>> I am somewhat confused by one thing, though.... > >>> > >>> If I do: > >>> > >>> > >>> enumerateDevices() => { device: id = 12345 type = videoinput } > >>> > >>> getUserMedia({video: { deviceId: { exact: 12345 } } > >>> > >>> enumerateDevices() > >>> > >>> am I guaranteed that the device with id 12345 in the second > >>> enumerateDevices is the same device as the one I grabbed? > >> > >> > >> OK so we need to be clearer about what persisting means. I meant persist (to disk) across browser sessions, leaving deviceIds stable "for the current session", by which I meant browser session, i.e. until you quit the browser. > > > > I think it needs to persist longer than that. It should persist until > > the OS can't associate it any longer. > > > > Here's a use case: set up Google chrome in kiosk mode (e.g. for a kiosk > > at an airport), run a video conference app on it that has two video > > cameras, e.g. face & document. You only want to have to associate device > > ids once, when you set up the hardware. Then store it to localStorage > > and reuse after every reboot. > > In kiosk mode locked down to a video conferencing application, I would > expect persistent permission to be granted during the setup process. > Yes, that's what I was trying to say. It needs to be possible to have persistent permissions AND a persistent identification of which camera is to be used for which purpose. At setup, you would associate a device id with a purpose, e.g 'this is the document camera and it always is rendered in this location on the web page and were always do OCR on an image taken from this". This info must persist across reboots, since the kiosk may be powered down every night. I'm just saying that it's not just the agrees permission that must persist, but also the device identification. HTH, Silvia.
Received on Tuesday, 7 July 2015 23:14:36 UTC