Home > Article > Web Front-end > Several storage methods of front-end HTML5
This article mainly introduces a summary of several front-end HTML5 storage methods, including local storage localstorage, local storage sessionstorage, offline cache (application cache), Web SQL, and IndexedDB. Those who are interested can find out.
Overall situation
Before h5, cookies were mainly used for storage. The disadvantage of cookies is that they carry data in the request header, and the size is within 4k. Main Domain pollution.
Main applications: shopping cart, customer login
For IE browser, there is UserData, the size is 64k, only IE browser supports it.
Goal
Solve the 4k size problem
Solve the problem that request headers often carry storage information Problem
Solving the problem of relational storage
Cross-browser
1. Local storage localstorage
Storage method:
Key-Value Storage method, permanent storage, never expires unless manually deleted.
Size:
5M per domain name
Support:
Note: IE9 localStorage does not support local files. You need to deploy the project to the server to support it!
Detection method:
if(window.localStorage){
alert('This browser supports localStorage');
}else{
alert('This browser does NOT support localStorage');
}
Commonly used API:
getItem //Get the record
setIten//Set the record
removeItem//Remove the record
key//Get The value corresponding to the key
clear//Clear the record
## Stored content:
Array, picture, json, style, script. . . (As long as the content can be serialized into a string, it can be stored)2. Local storage sessionstorage
In the local storage API of HTML5 The usage methods of localStorage and sessionStorage are the same. The difference is that sessionStorage is cleared after closing the page, while localStorage will always be saved.3. Offline cache (application cache)
Local cache of files required by the applicationHow to use:
①Configure manifest fileOn the page:...
Manifest File:
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: ①CACHE MANIFEST - files listed under this heading will be cached after the first download ②NETWORK - under this heading The outgoing files require a connection to the server and will not be cached③FALLBACK - The files listed under this heading specify the fallback page (such as a 404 page) when the page cannot be accessedFull demo:
##CACHE MANIFEST # 2016-07-24 v1.0.0 /theme.css /main.js NETWORK: login.jsp FALLBACK: /html/ /offline.html
On the server: manifest The file needs to be configured with the correct MIME-type, which is "text/cache-manifest". Such as Tomcat:
## Commonly used API:manifest text/cache-manifest
Core It is an applicationCache object and has a status attribute, indicating the current status of the application cache:
0 (UNCACHED): No cache, that is, there is no application cache related to the page 1 (IDLE): Idle , that is, the application cache has not been updated 2 (CHECKING): Checking, that is, the description file is being downloaded and checked for updates 3 (DOWNLOADING): downloading, that is, the application cache is downloading the description file The resources specified in 4 (UPDATEREADY): The update is completed and all resources have been downloaded5 (IDLE): Abandoned, that is, the description file of the application cache no longer exists, so the page The application cache can no longer be accessed Related events:Indicates a change in the application cache status:
checking: while browsing Triggered when the application cache is looking for updateserror: Triggered when an error is sent during checking for updates or downloading resourcesnoupdate: Triggered when checking the description file and finding no changes to the filedownloading: Triggered when downloading application cache resources starts progress: Triggered by continuous downloading during the process of file download application cache updateready: Triggered when the new application cache download on the page is completed cached: Triggered when the application cache is fully available Three advantages of Application Cache:① Offline browsing
② Improve page loading speed③ 降低服务器压力
注意事项：
1. 浏览器对缓存数据的容量限制可能不太一样（某些浏览器设置的限制是每个站点 5MB）
2. 如果manifest文件，或者内部列举的某一个文件不能正常下载，整个更新过程将视为失败，浏览器继续全部使用老的缓存
3. 引用manifest的html必须与manifest文件同源，在同一个域下
4. 浏览器会自动缓存引用manifest文件的HTML文件，这就导致如果改了HTML内容，也需要更新版本才能做到更新。
5. manifest文件中CACHE则与NETWORK，FALLBACK的位置顺序没有关系，如果是隐式声明需要在最前面
6. FALLBACK中的资源必须和manifest文件同源
7. 更新完版本后，必须刷新一次才会启动新版本（会出现重刷一次页面的情况），需要添加监听版本事件。
8. 站点中的其他页面即使没有设置manifest属性，请求的资源如果在缓存中也从缓存中访问
9. 当manifest文件发生改变时，资源请求本身也会触发更新
离线缓存与传统浏览器缓存区别：
1. 离线缓存是针对整个应用，浏览器缓存是单个文件
2. 离线缓存断网了还是可以打开页面，浏览器缓存不行
3. 离线缓存可以主动通知浏览器更新资源
4.Web SQL
关系数据库，通过SQL语句访问
Web SQL 数据库 API 并不是 HTML5 规范的一部分，但是它是一个独立的规范，引入了一组使用 SQL 操作客户端数据库的 APIs。
支持情况：
Web SQL 数据库可以在最新版的 Safari, Chrome 和 Opera 浏览器中工作。
核心方法：
①openDatabase：这个方法使用现有的数据库或者新建的数据库创建一个数据库对象。
②transaction：这个方法让我们能够控制一个事务，以及基于这种情况执行提交或者回滚。
③executeSql：这个方法用于执行实际的 SQL 查询。
打开数据库：
var db = openDatabase('mydb', '1.0', 'Test DB', 2 * 1024 * 1024,fn);
//openDatabase() 方法对应的五个参数分别为：数据库名称、版本号、描述文本、数据库大小、创建回调
执行查询操作：
var db = openDatabase('mydb', '1.0', 'Test DB', 2 * 1024 * 1024);
db.transaction(function (tx) {
tx.executeSql('CREATE TABLE IF NOT EXISTS WIN (id unique, name)');
});
插入数据：
var db = openDatabase('mydb', '1.0', 'Test DB', 2 * 1024 * 1024);
db.transaction(function (tx) {
tx.executeSql('CREATE TABLE IF NOT EXISTS WIN (id unique, name)');
tx.executeSql('INSERT INTO WIN (id, name) VALUES (1, "winty")');
tx.executeSql('INSERT INTO WIN (id, name) VALUES (2, "LuckyWinty")');
});
读取数据：
db.transaction(function (tx) {
tx.executeSql('SELECT * FROM WIN', [], function (tx, results) {
var len = results.rows.length, i;
msg = "查询记录条数: " + len + "
";
document.querySelector('#status').innerHTML += msg;
for (i = 0; i < len; i++){
alert(results.rows.item(i).name );
}
}, null);
});
由这些操作可以看出，基本上都是用SQL语句进行数据库的相关操作，如果你会MySQL的话，这个应该比较容易用。
5.IndexedDB
索引数据库 (IndexedDB) API（作为 HTML5 的一部分）对创建具有丰富本地存储数据的数据密集型的离线 HTML5 Web 应用程序很有用。同时它还有助于本地缓存数据，使传统在线 Web 应用程序（比如移动 Web 应用程序）能够更快地运行和响应。
异步API：
在IndexedDB大部分操作并不是我们常用的调用方法，返回结果的模式，而是请求——响应的模式，比如打开数据库的操作
这样，我们打开数据库的时候，实质上返回了一个DB对象，而这个对象就在result中。由上图可以看出，除了result之外。还有几个重要的属性就是onerror、onsuccess、onupgradeneeded（我们请求打开的数据库的版本号和已经存在的数据库版本号不一致的时候调用）。这就类似于我们的ajax请求那样。我们发起了这个请求之后并不能确定它什么时候才请求成功，所以需要在回调中处理一些逻辑。
关闭与删除：
function closeDB(db){
db.close();
}
function deleteDB(name){
indexedDB.deleteDatabase(name);
}
数据存储：
indexedDB中没有表的概念，而是objectStore，一个数据库中可以包含多个objectStore，objectStore是一个灵活的数据结构，可以存放多种类型数据。也就是说一个objectStore相当于一张表，里面存储的每条数据和一个键相关联。
我们可以使用每条记录中的某个指定字段作为键值（keyPath），也可以使用自动生成的递增数字作为键值（keyGenerator），也可以不指定。选择键的类型不同，objectStore可以存储的数据结构也有差异。
The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!
Related recommendations:
H5
Analysis of mobile REM layout adaptation method for active pages
The above is the detailed content of Several storage methods of front-end HTML5. For more information, please follow other related articles on the PHP Chinese website!