Storage - Revision history

Annevk at 00:22, 27 June 2015

2015-06-27T00:22:53Z

← Older revision		Revision as of 00:22, 27 June 2015
Line 1:		Line 1:
			{{obsolete\|spec=[http://storage.spec.whatwg.org/ Storage Standard]}}

	== Goals ==		== Goals ==

Annevk: /* API */

2015-04-16T04:12:20Z

API

← Older revision		Revision as of 04:12, 16 April 2015
Line 107:		Line 107:
	[Exposed=(Window,Worker)]		[Exposed=(Window,Worker)]
	interface StorageManager {		interface StorageManager {
	Promise<PersistentStoragePermission> requestPersistent();		[Exposed=Window] Promise<PersistentStoragePermission> requestPersistent();
	Promise<PersistentStoragePermission> persistentPermission();		Promise<PersistentStoragePermission> persistentPermission();

Annevk: /* Use cases */

2015-04-15T12:04:44Z

Use cases

← Older revision		Revision as of 12:04, 15 April 2015
Line 24:		Line 24:
	A social network wants to temporarily cache the latest activities locally.		A social network wants to temporarily cache the latest activities locally.

			=== Maps ===

			Have the directions to your destination abroad locally available so you can avoid roaming.

			=== News & books ===

			Have news articles or books available offline to read on the London Tube.

	== Infrastructure ==		== Infrastructure ==

Annevk: /* Why no eviction event? */

2015-04-15T12:01:42Z

Why no eviction event?

← Older revision		Revision as of 12:01, 15 April 2015
Line 168:		Line 168:
	=== Why no eviction event? ===		=== Why no eviction event? ===

	~~This~~ has been tried on other systems and they always end up with /tmp or some such. When you need space you don't want to ask a dozen applications to clear some before you can start allocating~~. You want to be able~~ to ~~wipe immediately. That is why priority-based temporary storage is preferable~~.		There are two main reasons to avoid this:

			* Does not allow for global reasoning by the user agent
			* Tragedy of the commons

			Also, this has been tried on other systems and they always end up with <code>/tmp</code> or some such. When you need space you don't want to ask a dozen applications to clear some before you can start allocating or ask the user to remove something.

	=== What is the relationship to the Quota API? ===		=== What is the relationship to the Quota API? ===

Annevk: /* API */

2015-04-07T15:53:28Z

API

← Older revision		Revision as of 15:53, 7 April 2015
Line 138:		Line 138:
	enum StorageMode { "atomic", "cache", "persistent" };		enum StorageMode { "atomic", "cache", "persistent" };
	enum PersistentStoragePermission { "default", "denied", "granted" }; // merge with NotificationPermission?		enum PersistentStoragePermission { "default", "denied", "granted" }; // merge with NotificationPermission?

			=== Rollout ===

			If this is too much at once, we can partition it as such:

			* v1: Persistent permission and usage/quota estimates.
			* v2: Boxes.

	== Existing APIs ==		== Existing APIs ==

Annevk: /* API */

2015-04-07T13:32:20Z

API

← Older revision		Revision as of 13:32, 7 April 2015
Line 95:		Line 95:
	Navigator implements NavigatorStorage;		Navigator implements NavigatorStorage;
	WorkerNavigator implements NavigatorStorage;		WorkerNavigator implements NavigatorStorage;

	This ensures the API is available everywhere under <code>navigator.storage</code>. (At some point we should probably clean up this pattern.)		This ensures the API is available everywhere under <code>navigator.storage</code>. (At some point we should probably clean up this pattern.)

Line 110:		Line 110:
	Promise<sequence<StorageBox>> boxes();		Promise<sequence<StorageBox>> boxes();
	};		};

	<code>StorageManager</code> provides access to getting permission for "persistent" boxes (and changing the origin storage unit's ''default box'' to use it).		<code>StorageManager</code> provides access to getting permission for "persistent" boxes (and changing the origin storage unit's ''default box'' to use it).

Line 119:		Line 119:
	The remainder provides access to ''boxes''. An origin storage unit's default box can be cleared by invoking <code>deleteBox()</code>. Invoking <code>deleteBox()</code> with a non-empty-string argument simply removes that box. <code>addBox()</code>'s first argument cannot be the empty string as it is reserved for the default box.		The remainder provides access to ''boxes''. An origin storage unit's default box can be cleared by invoking <code>deleteBox()</code>. Invoking <code>deleteBox()</code> with a non-empty-string argument simply removes that box. <code>addBox()</code>'s first argument cannot be the empty string as it is reserved for the default box.

	No access is given to a site storage unit for now as it crosses the ordinary security boundary.		Note: No access is given to a site storage unit for now as it crosses the ordinary security boundary.

	interface StorageBox {		interface StorageBox {

Annevk: /* Cache boxes */

2015-04-07T13:26:39Z

Cache boxes

← Older revision		Revision as of 13:26, 7 April 2015
Line 68:		Line 68:

	A "cache" box consists of a ''sequence of items''. What exactly constitutes an ''item'' is up to the API that supports a "cache" box. User agents are encouraged to reason globally about all ''items'' in all "cache" boxes in such a way that ''items'' the user least likely needs are cleared before others.		A "cache" box consists of a ''sequence of items''. What exactly constitutes an ''item'' is up to the API that supports a "cache" box. User agents are encouraged to reason globally about all ''items'' in all "cache" boxes in such a way that ''items'' the user least likely needs are cleared before others.

			Note: A "cache" box is distinct from an "atomic" (and "persistent") box in that it provides no all-or-nothing guarantees. It's ideal for storing resources that help improve performance but are not essential.

	==== Persistent boxes ====		==== Persistent boxes ====

Annevk: /* Cache boxes */

2015-04-07T13:22:06Z

Cache boxes

← Older revision		Revision as of 13:22, 7 April 2015
Line 67:		Line 67:
	==== Cache boxes ====		==== Cache boxes ====

	User agents are encouraged to reason globally about all '~~individual~~ items' in "cache" boxes in such a way that items the user least likely needs are cleared before others ~~without paying much heed to any perceived boundaries~~.		A "cache" box consists of a ''sequence of items''. What exactly constitutes an ''item'' is up to the API that supports a "cache" box. User agents are encouraged to reason globally about all ''items'' in all "cache" boxes in such a way that ''items'' the user least likely needs are cleared before others.

	==== Persistent boxes ====		==== Persistent boxes ====

Annevk: /* Atomic boxes */

2015-04-07T13:16:30Z

Atomic boxes

← Older revision		Revision as of 13:16, 7 April 2015
Line 61:		Line 61:
	==== Atomic boxes ====		==== Atomic boxes ====

	User agents are encouraged to reason globally about all "atomic" boxes in such a way that boxes the user least likely needs are cleared before others without paying much heed to site or origin storage unit boundaries. ~~If an~~ "atomic" ~~box needs to be cleared it needs to be cleared entirely~~.		An "atomic" box is cleared in its entirety. User agents are encouraged to reason globally about all "atomic" boxes in such a way that boxes the user least likely needs are cleared before others without paying much heed to site or origin storage unit boundaries.

			User agents could potentially reason globally about "atomic" boxes and individual items of "cache" boxes together.

	==== Cache boxes ====		==== Cache boxes ====

Annevk: /* Elsewhere */

2015-04-07T13:12:58Z

Elsewhere

← Older revision		Revision as of 13:12, 7 April 2015
Line 170:		Line 170:
	* https://github.com/w3c/quota-api/issues		* https://github.com/w3c/quota-api/issues
	* https://github.com/slightlyoff/StorageDurability/issues		* https://github.com/slightlyoff/StorageDurability/issues
			* https://bugzilla.mozilla.org/show_bug.cgi?id=1147820