W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 19803] "Fingerprint" is unclear

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Dec 2012 23:42:48 +0000
To: public-audio@w3.org
Message-ID: <bug-19803-5429-QiLl42vqrA@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19803

--- Comment #12 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> ---
(In reply to comment #10)
> I don't see how you're going to maintain that port B - in the enumeration of
> MIDI ports coming form the underlying hardware, not in the fingerprint
> stored by the app in local storage - has a modified entropy pool.  Every
> time you enumerate ports, you're going to start from zero with the
> fingerprint map - so if A was removed, B will be the "natural fingerprint
> available" port.  Yes?

I need to actually try this to be sure, but for example the Windows MIDI API
has the notion of device ID, which is actually a pointer to a HMIDIIN instance,
and it seems that even if the port's index has changed, the ID stays the same,
so you can actually see that port at index something has a pointer that's
already associated to a fingerprint. But I need to figure out if this is true,
and if something like this can be done on (at least) all desktop platforms. It
would be silly if you can't detect whether two midi port instances are actually
pointing to the same port.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 7 December 2012 23:42:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:03 UTC