A durable storage that I can trust the data won't be erased. If the data is erased, the app will simply not work offline all offline.
A caching storage to make the app faster, but loosing this data is not a problem as it can be refetched on demand.
I'm not sure to understand how I'm supposed to do. When requiring storage durability, does it apply to all browser storages, or can we create 2 different kind of storage like I'm trying to achieve?
As far as I understand, requiring durability is global, but there's an event storagepressure that I may listen to trigger myself a storage cleanup, right?
This work moved to https://github.com/whatwg/storage mostly. There's a rough plan for v2 to provide the second bullet point by allowing sites to allocate new storage boxes.
Hi,
This is related to https://github.com/slightlyoff/StorageDurability/issues/4
To build offline apps, I need the following:
I'm not sure to understand how I'm supposed to do. When requiring storage durability, does it apply to all browser storages, or can we create 2 different kind of storage like I'm trying to achieve?
As far as I understand, requiring durability is global, but there's an event
storagepressure
that I may listen to trigger myself a storage cleanup, right?