HTML5 Storage: Application Cache

Google Tech Talk January 5, 2011 Presented by Nikolas Coukouma. ABSTRACT HTML5 includes a specification for application caches. This unique feature allows a page to store needed static resources and start even when offline. This talk will cover both the basics and some more advanced uses. Hopefully it will answer most of your questions about what’s possible and provide some hints about how to do it.

4 Comments

  • Some questions. I have one website and let’s say I have two pages: /index and /test on those different pages I have also different static resources, but some resources that are in common.

    Should I create one manifest for each page and add there exactly required resources or could I have one manifest that is for all pages?

    Now for caching some resources I use ?v=1 and when I make an update I say ?v=2 (saying for css file), I can make something similar based on cache manifest?

  • @darkyndy You could do it either way. Some considerations: are both pages updated at the same time? how much overlap is there? are users likely to need to access both if they access one?

    Re: URL query params: putting the version on a comment line might be less risky; the explicit application cache entry ‘foo?v=1’ would not be used to serve ‘foo?v=2’ or ‘foo’ .

Leave a Reply

Your email address will not be published. Required fields are marked *