Re: Fixing appcache: a proposal to get us started

  > To prevent browser caching unsupported resources,
> the best approach I've found was to split the manifest
> file.

Sounds like the good way to go.

> This way we can tell browsers that support OGG files
> to cache only OGG files, and do tha same for other
> formats like MP3.

Nothing wrong here.

> But it is a "ugly solution". Now I have two manifest
> cache files, one with all OGG files listed (ogg.appcache)
> and the other one with the MP3 files (mp3.appcache).

This is the wrong way to go :)
Your manifest file should be dynamically generated by your server, based on
what you know about the user's browser.
Now you have one single manifest file which is easier for updates, +
server-side language comments so documentation is easy.

The web is server + client sides. Trying to "fix" issues you have with
client technologies only (appcache, JavaScript, ...) will always be a bad

Received on Monday, 25 November 2013 11:56:21 UTC