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

@gterzian commented on this pull request.



> @@ -419,6 +419,17 @@ which is either null or an [=/upgrade transaction=], and is initially null.
 
 </div>
 
+<!-- ============================================================ -->
+### Database storage ### {#database-storage}
+<!-- ============================================================ -->
+
+Indexed DB is a [=/storage endpoint=], with the [=/storage identifier=] `"indexedDB"`.
+
+A <dfn>pumpkin</dfn> is a [=/struct=] consisting of a <dfn for="pumpkin">queue</dfn> (a [=/connection queue=]) and a <dfn for="pumpkin">database</dfn> (a [=/database=]).

Why are you putting the queues in the map? 

Looking at the current spec, which at [database-construct](https://w3c.github.io/IndexedDB/#database-construct) reads: "Each [storage key](https://storage.spec.whatwg.org/#storage-key) has an associated set of [databases](https://w3c.github.io/IndexedDB/#database).", I think what you need is rather for the map to contain just that set of databases. 

But it's not completely clear to me what a https://storage.spec.whatwg.org/#storage-proxy-map exactly is. Looking at how it is used in https://html.spec.whatwg.org/multipage/webstorage.html#concept-storage-map, it looks like the proxy to the actual database. But not sure how well that would fit in the indexeddb spec. 

At the end of the day, the main goal of the map is to be able to compute things like the https://storage.spec.whatwg.org/#storage-usage and to determine whether it is persisted or not, right?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/pull/334#pullrequestreview-3954382427
You are receiving this because you are subscribed to this thread.

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