- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Mon, 10 Dec 2012 08:13:08 +0100
- To: "Timothy B. Terriberry" <tterriberry@mozilla.com>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2012-12-07 18:23, Timothy B. Terriberry wrote: > Adam Bergkvist wrote: >> Could we have a solution where the selector UI is always shown even >> though no "real" devices met the mandatory constraints? In that case you >> could still select a file to emulate, e.g., a camera. > > I'm curious to hear how you think this should interact with the deviceId > constraint proposed earlier. Do all files use the same deviceId (even > though they may have, for example, drastically different resolutions and > framerates)? I liked your explanation with "user empowerment" (in some previous mail) regarding the option to select a file instead of a device. So I think a requirement for this is that the app shouldn't be able to sniff that the user is using a file instead of a device. So if two files with totally different characteristics had the same device id, perhaps the app could detect that and guess that the user is "cheating" into the service and lock the user out. > If not, is the deviceId they do have persistent (so an app > could request the exact same file it had before)? Do your answers to > these questions change if we allow enumeration of deviceIds or merely > allow re-requesting a previously obtained deviceId? Having a separate device id for every file and at the same time support enumerating all devices ids without ever having used any devices would be bad. :) But then, I don't like the idea of enumerating device ids for devices that hasn't gone through the getUserMedia() process at least once. /Adam
Received on Monday, 10 December 2012 08:59:42 UTC