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 21:10:24 +0000
To: public-audio@w3.org
Message-ID: <bug-19803-5429-obLf04ROzw@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19803

--- Comment #7 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #6)
> Not sure how to word this in the spec. Would it be worth dictating this,
> regardless of how good the implementation is at producing unique
> fingerprints?

Hmm.  Well, the problem is that you can't come up with an ideal identifier,
right?  If I record in the fingerprint "this is MOTU MIDI Express input port #1
of 16", and then when I go to recreate based on that fingerprint there are only
8 ports with that name/manufacturer/version, I don't know if #1 of 8 is the
right port or not (I don't know if they disconnected the first interface/8
ports or the second 8).  I couldn't think of an algorithm good enough to
dictate; the best I could do would be "look for a name match, and match "#n of
m ports with this name" - if the number of ports with this name ("m") has
changed, just fail.  That would take care of "unplugging my AKAI USB keyboard
controller doesn't make my Launchpad assignments stop working," but the above
case (I unplug one of my identically-named interfaces) would fail.  What do you
think of that?  Your code example is missing too many function implementations
for me to completely confirm, but I think that's essentially what it's doing?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 7 December 2012 21:10:26 UTC

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