Re: [w3c/IndexedDB] Define Indexed DB as a storage endpoint, use hooks (#334)

Partial update. I needed a name for the (queue,database) struct that exists in the map. I literally called it **pumpkin** here as a placeholder name because I wasn't feeling inspired. So bikeshed away!

This drops the need for most of the imports from Storage, although these are retained:
* **storage bucket** - which exists in the published version, so not new in this PR; this is used to reference durability
* **storage identifier** - this is informative, used in the phrase _Indexed DB is a storage endpoint, with the storage identifier "indexedDB"._ which isn't really necessary but looks nice? We can remove, since it's a registered end point and we don't need to define it. Thoughts?

Most of the remaining references to "origin" end up being fairly illustrative rather than normative definitions. We could probably scrub most of them e.g. "if the origin’s storage is cleared" → "if the storage is cleared".

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/pull/334#issuecomment-1146484719

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/pull/334/c1146484719@github.com>