On Wed, Dec 10, 2008 at 3:53 PM, Erik Kay <[EMAIL PROTECTED]> wrote: > In general, my preference would be to have a single id for the > extension. Multiple id's seem to always end in pain and hurting. We > already have one id that we know we have to have - the public key. > This is what we're going to use for autoupdate and blacklisting. > However, the public key is far too unwieldy for general use in > referring to the extension in code and on the filesystem.
I imagine for blacklisting we'll use what people typically use when referring to a public key -- its fingerprint. Those are about as long (in terms of filename characters) as a com.google.foo namespace, and it keeps us down to one GUID (the public key) rather than two (pubkey and java-style namespace). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
