W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Fixing appcache: a proposal to get us started

From: Emerson Estrella <emerson.estrella@gmail.com>
Date: Wed, 27 Mar 2013 02:03:33 -0300
Message-ID: <CAMhJiGDjd=f_ZAYb_xrP_gTqGj7ju0d_g5=TV19CM9q7oGUGqA@mail.gmail.com>
To: public-webapps@w3.org
I'm writing a web application that uses the AppCache API for offline
browsing. But I'm also using the Audio API to play back-ground music and a
few audio effects.


For audio support in different browsers I'm delivering each sound/music in
two different file formats: OGG and MP3.


The problem is regarding the cache manifest file. If we add all audio files
(MP3 and OGG) in the cache manifest file, all browsers will cache all
files. Including the unsupported ones. So, we end up with a huge
storage requirement. Which is really bad if you are on a 3G connection for
example.


To prevent browser caching unsupported resources, the best approach I've
found was to split the manifest file. This way we can tell browsers that
sopport OGG files to cache only OGG files, and do tha same for other
formats like MP3.


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).



Good luck guys!


Best regards,

Emerson Estrella
Received on Wednesday, 27 March 2013 07:44:23 GMT

This archive was generated by hypermail 2.3.1 : Wednesday, 27 March 2013 07:44:24 GMT