[whatwg/storage] Meta: Best practices for storage-related specs to define their parallel queues (Issue #194)

asutherland created an issue (whatwg/storage#194)

As part of @monica-ch's deeply appreciated work to clean up the "in parallel" algorithms in the ServiceWorkers spec, a question has been raised in https://github.com/w3c/ServiceWorker/pull/1842#pullrequestreview-4868895938 about how best to define these queues and so I thought I would raise the question here for discoverability for other storage-related specs facing this issue and since possibly any advice could go in the spec[1].

I'll quote the question from there below:
> Quick clarification before I push: https://github.com/w3c/ServiceWorker/pull/1838 hangs the queue off `[=name to cache map=]` because that map is itself per-storage-key. Clients don't have an equivalent map — the `[=/service worker clients=]` list is UA-wide, filtered by storage key. Would you prefer a UA-level `<dfn>Clients parallel queue</dfn>` map keyed by storage key, or a prose "for each storage key, the UA has an associated Clients parallel queue" form?

1: For example, maybe queues that are 1:1 with bottles could be called straws... (joke!)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/issues/194
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/storage/issues/194@github.com>