开源软件名称：

ImmortalDB

开源软件地址：

https://gitee.com/mirrors/immortaldb

开源软件介绍：

ImmortalDB

ImmortalDB is a resilient key-value store for the browser.

ImmortalDB is the best way to store persistent key-value data in thebrowser. Data saved to ImmortalDB is redundantly stored inCookies,IndexedDB, andLocalStorage,and relentlessly self heals if any data therein is deleted or corrupted.

For example, clearing cookies is a common user action, even for non-technicalusers. And browsers unceremoniouslydeleteIndexedDB, LocalStorage, and/or SessionStorage without warning under storagepressure.

ImmortalDB is resilient in the face of such events.

In this way, ImmortalDB is likeEvercookie, but

Is actively maintained and well documented.
Provides a simple, modern, Promise-based API.
Strikes an equitable balance between reliability and respect for theuser. Data is stored reliably but can also be voluntarily purged if theuser designedly clears cookies and application storage.
Doesn't use nefarious exploits nor deprecated third party plugins likeFlash, Silverlight, or Java. Only standard, ratified HTML5 APIs are used.
Doesn't vandalize performance or the user experience. For example,Evercookie's CSS History Knocking can beget a deluge of background HTTPrequests, and loading Silverlight or Flash can raise unsought permissionmodals or thrash the user's disk.

How ImmortalDB works.

When you store a key-value pair in ImmortalDB, that key and value aresaved redundantly in the browser's cookies, IndexedDB, and LocalStoragedata stores.

When a value is retrieved via its key, ImmortalDB

Looks up that key in every data store.
Counts each unique returned value.
Determines the most commonly returned unique value as the 'correct' value.
Returns this correct value.

Then ImmortalDB self-heals: if any data store(s) returned a value different thanthe determined correct value, or no value at all, the correct value is rewrittento that store. In this way, consensus, reliability, and redundancy ismaintained.

API

Set

ImmortalDB's API is simple. To store a value, use set(key, value):

import { ImmortalDB } from 'immortal-db'await ImmortalDB.set('key', 'value')

key and value must beDOMStrings.ImmortalDB.set(key, value) also always returns value, so it can be chained orembedded, like

const countPlusOne = (await ImmortalDB.set('count', numberOfClowns)) + 1

Get

To retrieve a value, use get(key, default=null):

const value = await ImmortalDB.get('key', default=null)

get() returns the value associated with key, if key exists. If keydoesn't exist, default is returned. key must be aDOMString.

Remove

Finally, to remove a key, use remove(key):

ImmortalDB.set('hi', 'bonjour')console.log(await ImmortalDB.get('hi'))  // Prints 'bonjour'.await ImmortalDB.remove('hi')console.log(await ImmortalDB.get('hi'))  // Prints 'null'.

key must be aDOMString.

Data Stores

The data stores that ImmortalDB stores data in can also be configured.For example, this is how to store data reliably in cookies andLocalStorage only:

import { ImmortalStorage, CookieStore, LocalStorageStore } from 'immortal-db'const stores = [await CookieStore(), await LocalStorageStore()]const db = new ImmortalStorage(stores)await db.set(key, JSON.stringify({1:1}))

By default, stores used by ImmortalDB are:

CookieStore -> Keys and values are stored in document.cookie.
IndexedDbStore -> Keys and values are stored in window.indexedDB.
LocalStorageStore -> Keys and values are stored in window.localStorage.

Other, optional stores are:

SessionStorageStore -> Keys and values are stored in window.sessionStorage.

New storage implementations can easily be added, too; they need onlyimplement the async methods get(key, default), set(key, value), andremove(key).

Installation

Installing ImmortalDB with npm is easy.

$ npm install immortal-db

Or include dist/immortal-db[.min].js and use window.ImmortalDB directly.

<html>  <head>    <script src="immortal-db.min.js"></script>    <script>      ;(async () => {        const db = ImmortalDB.ImmortalDB        await db.set('hi', 'lolsup')      })()    </script>  </head>  ...</html>