Our Web-Application uses Application cache (cache manifest) to restore HTML page and resources in off-line mode. HTML-pages have sessionIDs as params in URI. So, after each logout and login action new HTML-pages are saved to application cache because sessionId was changed in URI. After some weeks working with application some browsers start work slower. And size of Application cache (tested on FF 3.6+) is about 200Mb! After each logout we clear LocalStorage of browser,but how to clear resources from Application storage?
2 Answers
The problem with the application cache taking up so much space is that you are giving the user agent a different offline web application each time. An offline web application is identified to the user agent by the URI of the cache manifest file, including query string - not the URI of the master file as you might think.
Thus, by including the session ID in the cache manifest URI, you're telling the browser that each session gets its own brand new application without using any of the previously downloaded ones (and thus, never being able to clear them out). You're installing a different web application every time.
Reconsider how you're architecting your application, as currently using HTML5 offline cache manifest is providing no value - just causing excessive downloading. The architecture that web applications encourage is serving all HTML statically, and fetching data that requires sessions via AJAX. Web applications don't work when built in the classic "dynamically generate an HTML page with data on the server" paradigm.
1 Comment
SAHbKA
The problem is fixed by temporary solution: client gets sessionId via cookies and URI to manifest file doesn
t include sessionID-as a result the only one ApplicationCache object in browser with static name(without sessionId). @Stoive- sorry, cant add reputation bkz I`m a new user here:)I'm not sure you do have control over application cache from JavaScript. This is something which should be handled by the browser and the user when clearing the cache.
3 Comments
SAHbKA
The main problem is that users who use our web-Application do not have rights to clear cache from browser using standard methods of browser. The devices(OS,browser) is limited very much and browser Options are restricted for them
jonjbar
Perhaps the following extension might help ? sites.google.com/site/keigoattic/home/…
Stoive
You can manually trigger an update through JavaScript, but that's about it: whatwg.org/specs/web-apps/current-work/multipage/…
mysite.com/?SID=123456&a=1 mysite.com/?SID=123456, So, static pages are downloaded and saved to cache. Each Logout/login generate new sessionId that leads to storing new static pages.