Browser Cache Vs HTML5 Application Cache

HTML5 Cache

HTML5 provides application cache, which means that a web application is cached, and accessible without an internet connection. Application cache gives an application three advantages:

• Offline browsing - users can use the application when they're offline

• Speed - cached resources load faster Reduced server load - the

• browser will only download updated/changed resources from the server

Browser cache

Internet browsers use caching to store HTML web pages by storing a copy of visited pages and then using that copy to render when you re-visit that page. If the date on the page is the same date as the previously stored copy, then the computer uses the one on your hard drive rather than re-downloading it from the internet.

References -

• http://www.w3schools.com/html/html5_app_cache.asp

• http://www.pctools.com/security-news/what-is-a-browser-cache/

The new HTML5 specification allows browsers to prefetch some or all of a website assets such as HTML files, images, CSS, JavaScript, and so on, while the client is connected. It is not necessary for the user to have accessed this content previously, for fetching this content. In other words, application cache can prefetch pages that have not been visited at all and are thereby unavailable in the regular browser cache. Prefetching files can speed up the site's performance, though you are of course using bandwidth to download those files initially.

AppCache has been deprecated.

See Google's note on it and Mozilla's. Google recommends using the service worker Cache API (which Mozilla classifies as an "experimental technology"). Note: compatibility with Safari is limited.