Cache Manifest Size Limit and Web Apps

VolatileStorm picture VolatileStorm · Jul 20, 2011 · Viewed 32.4k times · Source

I am in the planning phases for writing an application, still choosing the technology that I wish to use to write the app. The initial idea was to write a web-app but this has (had?) the downfall of being unable to be viewed offline. I then discovered cache manifest, and this potentially seemed like an answer.

However, since that first point it seems that there are size limits on Cache Manifest. I can't find a full list of the size limits for each browser, so I can't tell if it's completely debilitating (though I think it may be). The browsers that I wish the app to work on are Firefox, Chrome and the mobile Safari browsers (that is, it has to work on iPad).

My understanding is that in most cases there is a total cache limit of about 5MB (with it varying from browser to browser), but this would not be enough for my needs. I'm looking to store all of the users online data offline. This includes things like uploaded files (PDFs, pictures) as well as the content required to make the app physically work. In any example I've seen, cache-manifest has only been used to cache offline things like the html, the css, the javascript and the image resources of the website. Is it suitable for offline storage of PDFs the user has uploaded?

If the answer to this question is a resounding no (which I fear that it may be), are there any other solutions? Or is a "proper" app in a browser - that is, one with a reasonable space requirement - completely infeasible at this time? Are we still waiting for the browsers to catch up with the requirements of development?

Edit: Just to add, I am aware that there is no limit on Cache-Manifest in the HTML5 specification, but the implementations all seem to limit it, and this will affect anything I attempt to write.

Answer

KimKha picture KimKha · Apr 15, 2012