- From: Marcos Caceres <w3c@marcosc.com>
- Date: Wed, 11 Dec 2013 13:48:19 +1000
- To: public-webapps@w3.org
Would any potential implementer consider supporting a HTTP based solution to loading manifests? The rationale being: "For manifests it is much more commonly going to be the case that there's existing content that people want to add a manifest to. Doing that by editing each and every HTML file or HTML-outputting server side script seems likely to in many cases be much harder than adding a config setting [on the server] that adds a link header." It would mean using something like the HTTP `Link:` header defined in [RCF5988] or a new HTTP header like `Manifest:`. So, something like the following in the case of [1]: Link: </manifest.json>; rel="manifest" Or the following in the case of a new header: Manifest: /manifest Please see the following for discussion: https://github.com/w3c/manifest/issues/98 [RFC5988] http://tools.ietf.org/html/rfc5988 -- Marcos Caceres
Received on Wednesday, 11 December 2013 03:48:50 UTC