Why is the update manifest in XML? The extension manifest is in JSON, and it is much more pleasant to work with than XML. The Omaha folks surely realize we are not in the late 90's anymore...
Peace uriel On Tue, Aug 11, 2009 at 7:23 AM, Aaron Boodman<[email protected]> wrote: > > There is no need to do this manually. Chrome has its own extension > update system built-in. You can learn more about it here: > > http://dev.chromium.org/developers/design-documents/extensions/autoupdate > > You should avoid doing your own automatic updates as it is difficult > to do them in a secure way. Instead, use the built in updater if you > can. > > - a > > On Mon, Aug 10, 2009 at 8:04 PM, Maxo<[email protected]> wrote: >> >> This is my first attempt at writing an extension, and I am only just >> passed being a beginner at Javascript, so forgive me for the newb >> question. I want my extension to check for an updated configuration >> file that resides on the web each time Chrome starts up. I tried >> using XMLHttpRequest, but that fails because of Cross Site Scripting >> security. >> I am also using a content_script, which is not optimal because it >> fires off each time a new tab is opened, which could cause performance >> issues and is overkill. I just want to get the new file each time the >> browser is loaded. What is the best way to tackle this? >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
