On Thu, May 7, 2009 at 4:20 PM, Adam Barth <[email protected]> wrote: > On Thu, May 7, 2009 at 4:17 PM, Aaron Boodman <[email protected]> wrote: >> Ok, thanks for the recommendation. Currently the magic string is >> "Cr24". Not enough characters? > > I suggested the above to be analogous to HTML5's appcache manifests: > > http://www.whatwg.org/specs/web-apps/current-work/#a-sample-manifest > > In general, the closer you are to that, the more predictable the web becomes.
Just to clarify, you understand we're talking about a binary package here, right? Not a text file. Chrome extensions are distributed in what are essentially zip files with some extra metadata tacked on. The first several bytes of that zip file is currently always "Cr24". You're saying it should be "CHROME EXTENSION" instead. Is there any specific value in being closer to the way the appcache manifests work, other than having a longer signature? - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
