Re: [w3c/ServiceWorker] Editorial: use a dedicated parallel queue for the Clients API (PR #1842)

@monica-ch commented on this pull request.



> +    Each {{Clients}} object has an associated <dfn>Clients parallel queue</dfn> (a [=parallel queue=]) used to serialize the {{Clients}} object's operations.
+

Agreed, 1-per-`Clients` is under-constrained. Will rework to 1-per-storage-key matching #1838.

Quick clarification before I push: #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?


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1842#discussion_r3724486350
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1842/review/4869298881@github.com>