Hi. I don't know if you guys had the opportunity to work with HTML5 AppCache. Well, we have 2 big features with AppCache: Offline Application and Optimize load time of your page. I think that for the first purpose it's everything fine. About the second, we have some issues. It's amazing to have total control of the user cache, and i think this is very promising. The main issue in AppCache is that the current document is appcached. This means that, if you have a single page, and you want to cache just images, css and JavaScript, you can't. Why? Because the espec says: "Regardless of whether you include the address of the current page in the manifest, it will be cached" This sucks, because in real life web apps, that i want to save requests and Kbytes, not necessarily i want to cache the current page. Actually, i dont want to cache the content of my current page. We have another rule from spec: "With the exception of “no-store” directive, HTTP cache headers are overridden by manifests" In Firefox and Opera, this works fine, but not in Google Chrome. It seems that Chrome ignores Cache-Control:no-store, and with this, my current page is ever cached. I posted about this in my blog http://jaydson.org/en/html5-appcache-cache-control-no-store and i want know if some of you guys have a solution, or workaround for that. I found a post http://saikotroid.blogspot.com/2011/06/application-cache-whitelisting-master.html where someone suggested an workaround with iframe. Seems that it works. Tks.
-- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
