Re: [w3c/ServiceWorker] Abstracting cache matching (#1341)

wanderview commented on this pull request.



> @@ -1656,20 +1656,23 @@ spec: webappsec-referrer-policy; urlPrefix: https://w3c.github.io/webappsec-refe
     <pre class="idl">
       [SecureContext, Exposed=(Window,Worker)]
       interface Cache {
-        [NewObject] Promise&lt;any&gt; match(RequestInfo request, optional CacheQueryOptions options);
-        [NewObject] Promise&lt;FrozenArray&lt;Response&gt;&gt; matchAll(optional RequestInfo request, optional CacheQueryOptions options);
+        [NewObject] Promise&lt;any&gt; match(RequestInfo request, optional MultiCacheQueryOptions options);

Can you explain why methods on the Cache object would take a `cacheName` value via the `MultiCacheQueryOptions`?  It seems like the Cache object should be locked to itself and not be able to query other cache objects.

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