W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > April 2015

Re: [mediacapture-main] Premature optimization in enumerateDevices steps

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Wed, 08 Apr 2015 15:12:58 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-90946441-1428505977-sysbot+gh@w3.org>
I guess it's there to guard against the steps that follow which 
dictate device probing in direct response to each enumerateDevices 
call (a polling model). 

What's odd is that we now also support 'ondeviceschanged' (a push 
model), making the obvious place to update any global internal list of
 devices be right before we fire that event.

There's still a reason to build a list uniquely for each (session of 
an) enumerateDevices call: make the IDs origin-unique, but I'm not 
sure the amount of CPU needed to do that warrants having the spec 
optimize around it for us.

I feel there's a better way to word this, but it's escaping me at the 

GitHub Notif of comment by jan-ivar
Received on Wednesday, 8 April 2015 15:13:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 October 2017 05:05:41 UTC