application-cache

问题 Quick question for discussion really, as I wanted to have input from different people. I am in the process of developing a web page app that must be available offline. Now to do this, as I understand it, you would go about using either the application caching feature or by using service workers. However, here is the conundrum I have. When researching the application cache, the MDN clearly states: Deprecated: This feature has been removed from the Web standards. Though some browsers may still

问题 I am developing a web app for offline use, thus I need to use the application cache functionality. Everything works great on Chrome (15.0.874.106) but is doesn't work on Firefox (7.0.1) and Opera (11.52). This is my cache manifest file cache.manifest.php (I have reduced it to the bare minimum): <?php header("Cache-Control: max-age=0, no-cache, no-store, must-revalidate"); header("Pragma: no-cache"); header("Expires: Wed, 11 Jan 1984 05:00:00 GMT"); header('Content-type: text/cache-manifest');

问题 I have a versioned cache manifest: #version = e5b4271 Every time this version changes, my webapp loads the new manifest, but it never loads update files from the server. Even when I clear the browser cache (not the application cache itself), or hit Ctrl+Shift+R to force it to fetch a new version, it still loads the files from the old appcache. The only way I can get it to update is to clear the browser's application cache in settings, but obviously this is unacceptable because I need it to

问题 I have a SPA (Single-Page Application) written using OpenUI5 framework. It works well (when I'm in debug mode or using cache-killer https://chrome.google.com/webstore/detail/cache-killer/jpfbieopdmepaolggioebjmedmclkbap) but now I have pushed the app on the server apache: here the problems started... Users not have cache-killer installed and I would like update the app on the server and immediately have the new version of the app on the users pcs at the successive refresh. In my app I have a

问题 i am writing an offline web application. i have a manifest files for my applicationCache. and i have handlers for appCache events. i want to detect if the files being downloaded are being downloaded for the first time or being updated. because in case they are being updated, i would like prevent my application code from running, since i will refresh the browser after updating my app. my specific problem here is that when the "checking" events gets fired, the applicationCache status is already

问题 I may get some heat for this question because there are a lot out there already. BUT... Every question has a different answer and no finite answer seems to be solid. SO THE QUESTION... If I update a file which is reference in the application cache manifest for an offline available application, how can i force the update of the manifest and the offline cache without changing the manifest? I hope this is clear. To show that I have done some research: How to properly invalidate an HTML5 Cache

问题 This is an odd thing I've just run into. I have a web application with a small DataTable stored in the ApplicationCache to reduce the amount of queries to a separate since the data is a lookup table that doesn't change often. I access this DataTable twice within a given page. Once to bind the data to a drop down list in my Page_Load method: dtDeptDivAct = GetAllDeptDivActCodes() dtDeptDivAct.DefaultView.Sort = "LongDescription ASC" ddlDeptDivAccount.DataSource = dtDeptDivAct.DefaultView

问题 Since I don't have all the devices & iOS versions available at hand, it's difficult to understand some of the issues my client is experiencing on older devices (namely iPad 1 and 2, both running iOS 5 [unsure of minor version]). Is there any documentation on how each of the iOSes respond to a webapp reaching it's cache size limit? ( 5MB supposedly? or I could be wrong, might just apply to the Web SQL Database size ) Also is the cache size limit the same across all devices & iOS versions? Note

问题 So I've got an application that stores offline data using an ApplicationCache. Long story short, it's silently dying for users who don't have offline data enabled, most commonly because they've got history turned off or are using private browsing, and I'd like to catch this and give the user a clear error. It appears that this can be detected by checking the cache's state, which will return 0 UNCACHED when there is no cache... but I'm not sure if that means that there is no cache yet , or

问题 I'm working on an app that lets users record voice (among other things) to the Documents directory of the app. But when I'm recording the voice, I'm recording to the caches directory of the app and then after the user says "Okay, save this one", then I'm coping it to the Documents directory. So far all these work. But if I try to delete the data file in cache, or when I try to move it, I get problems. So my question is, shall I just leave the data in cache so that iOS will handle it or do I