Just as some additional data, we used GUIDs for ids in Firefox
initially, since they were uniquer, but they proved to be a pain on
the file system, where it was hard to tell one directory with a
gobbledegoop name from another. So we added support for contract id
names which allowed the provider more flexibility
(com.foo.bar/myextension). This made life for developers a little
easier. I never heard of conflicts becoming an issue.
In practicality, the possibility of collision exists in many other
places on your computer: C:\Program Files\* or /Applications/* are two
good examples.
-Ben
On Wed, Dec 10, 2008 at 1:34 PM, Aaron Boodman <[EMAIL PROTECTED]> wrote:
>
> On Wed, Dec 10, 2008 at 12:09 PM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
>>
>> Ojan brought this up before, but I think it's a good idea, so I'll
>> evangelize it some more. Instead of requiring the extension developer
>> to come up with an extension ID (com.google.myextension), use
>> templating to automatically substitute a guaranteed unique ID where
>> needed. The template substitution would be done in the browser
>> process before we handed the script off to a renderer. Examples:
>> - img.src = "${EXTENSION_URL}/foo.gif";
>> - var extension = new chromium.Extension("${EXTENSION_ID}");
>
> It is a good idea. Part of the reason I brought back the short ID was
> we found two places it was useful (here, and as a name for
> directories) and I was worried we were going to keep coming up with
> examples like that. Also, it seems like using a public key as an ID is
> overkill in case we ever have SSL-served extensions.
>
> On the other hand, there is a lot of charm to only having the public
> key as an identifier in the case of packaged extensions. And I'm not
> that concerned about the escaping issues.
>
> Let me think on it some more. Erikkay -- any thoughts on this?
>
> - a
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
