Do I need to stick images?

Question

The biggest problem that I encountered when using the HTML5 appcache features was that there were too many files to load and update the cache very slowly. Images are the biggest culprit because they are large and cannot be combined into a single file, and downloading / caching many files is a particular problem on mobile devices. Also, on iOS devices, there seems to be a problem pulling out appcache'd resources, even for a modest webapp, this process takes several minutes. Thus, reducing the number of files in appcache only on mini-JavaScript and CSS file makes the process much faster.

What I ended up with is completely removing the images from the cache manifest and allowing them to be saved in the traditional browser cache. I tested various devices, browsers, etc. And I can pull my webapp offline and all the images load just fine. If the images are static enough, is there any problem that can be seen just relying on traditional caching?

Answer 1

The only reason you should use appcache is the constant offline content.

I could be cached in the browser for a while, but this does not guarantee that it will remain cached. The OS may decide to clear the cache when it is low in memory.

, , . .

; , .