On 08/31/2012 09:55 PM, Jonas Sicking wrote: > There are a few ways we can provide this information. > > 1. Have the metadata available in a separate JSON file and add a > property which links to package. > 2. Have the metadata available in a separate JSON file and add a > property in the webapp manifest in the app package which links to the > metadata JSON. > 3. Have the metadata available in a separate JSON file. Make the > installPackage function take two URLs, one to the metadata JSON, and > one to the app package. > 4. Make the metadata available through headers when making a GET or > HEAD request to the package. > 5. Have the metadata available in a separate JSON file, and use > headers to link to that when making a GET or HEAD request to the > package. > > I think that the best solution of the above is 1. I.e. have a JSON > file which contains all the needed metadata as well as the URL of the > actual app package. The JSON file could follow the format of the > webapp manifest as much as possible, though that's likely limited to > mostly the localization parts.
Perfect. Let's ship it. :) Wil _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
