Home > Article > Web Front-end > Webkit's Research on Application Cache Implementation of HTML 5_html/css_WEB-ITnose
Due to work, I have been studying ApplicationCache for a while. First, let’s introduce some basic concepts of SQL DB Table related to it,
For more introduction, please refer to the article from w3school.com.cn:
Using HTML5, through Create a cache manifest file to easily create an offline version of your web application.
HTML5 introduces application caching, which means web applications can be cached and accessed without an Internet connection.
Application caching brings three benefits to apps:
Application caching is supported by all major browsers except Internet Explorer.
The following example shows an HTML document with cache manifest (for offline browsing):
<!DOCTYPE HTML><html manifest="demo.appcache"><body>The content of the document......</body></html>
Try it yourself
To enable application caching, include the manifest in the document's tag Attributes:
<!DOCTYPE HTML><html manifest="demo.appcache">...</html>
Each page with a specified manifest will be cached when the user accesses it. If the manifest attribute is not specified, the page will not be cached (unless it is specified directly in the manifest file).
The recommended file extension for manifest files is: ".appcache".
Please note that the manifest file needs to be configured with the correct MIME-type, i.e. "text/cache-manifest". Must be configured on the web server.
Manifest files are simple text files that tell the browser what is cached (and what is not cached).
The manifest file can be divided into three parts:
The first line, CACHE MANIFEST, is required:
CACHE MANIFEST/theme.css/logo.gif/main.js
The manifest file above lists three resources: a CSS file, a GIF image, and a JavaScript document. When the manifest file loads, the browser downloads these three files from the root directory of the website. Then, whenever the user disconnects from the Internet, these resources are still available.
The following NETWORK section specifies that the file "login.asp" will never be cached and is not available offline:
NETWORK:login.asp
You can use Star number to indicate that all other resources/files require an Internet connection:
NETWORK:*
The FALLBACK subsection below specifies that if an Internet connection cannot be established, "offline.html" is used instead of /html5 / All files in the directory:
FALLBACK:/html5/ /404.html
Note: The first URI is the resource, the second is the fallback.
Once an app is cached, it remains cached until:
CACHE MANIFEST# 2012-02-21 v1.0.0/theme.css/logo.gif/main.jsNETWORK:login.aspFALLBACK:/html5/ /404.html
重要的提示:以 "#" 开头的是注释行,但也可满足其他用途。应用的缓存会在其 manifest 文件更改时被更新。如果您编辑了一幅图片,或者修改了一个 JavaScript 函数,这些改变都不会被重新缓存。更新注释行中的日期和版本号是一种使浏览器重新缓存文件的办法。
请留心缓存的内容。
一旦文件被缓存,则浏览器会继续展示已缓存的版本,即使您修改了服务器上的文件。为了确保浏览器更新缓存,您需要更新 manifest 文件。
注释:浏览器对缓存数据的容量限制可能不太一样(某些浏览器设置的限制是每个站点 5MB)。