4 ms·

Appcache may not be the best approach for new work. It is deprecated and not recommended for future use. https://developer.mozilla.org/en-US/docs/Web/HTML/Usin

• brazzledazzle 11y ago
  It says that service workers are the replacement but on the service workers page cautions that they are experimental technology and the spec isn't finalized[1]. If you're deploying a new application which should you use? [1] https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...
  • daleharvey 11y ago
    I use service workers for side projects that only target new browsers, and appcache for everything else.
  • mtberatwork 11y ago
    Service Workers is a definite game changer. However, one thing to remember when implementing them is that you will need to be entirely on HTTPS.
• dspillett 11y ago
  That is a pain. I've got a project in early stages that is using AppCache to deal with disconnected use, and AppCache's replacement isn't commonly available yet. Then again I'm using AppCache as lightly as possible to get around some of the issues people report, essentially managing my own cache in one or more of the local storage options and just using AppCache for the stub that primes/updates the core code in that cache, so switching to using another option just as lightly might not be difficult. I'll have to read around Service Workers and make sure I'm not arranging to shoot myself in all three feet...