caches.match() could resolve immediately after first match is found |
|
Issue descriptionThe `caches.match()` algorithm inspects all of the caches for a matching resource and returns the first found. The search can abort after a response is discovered. Currently, though, chromium continues to search all of the caches before returning any results: https://cs.chromium.org/chromium/src/content/browser/cache_storage/cache_storage.cc?l=1052-1071&rcl=96e58815e52961e857d8ad1eb9d9ce65f41099e8 This code queues up a separate task to match against each cache. These tasks run in sequence. The BarrierClosure callback is only called after all of them complete.
,
Sep 16
I would like to fix this issue if no one working on this. :)
,
Sep 17
> I would like to fix this issue if no one working on this. :) No one is directly working on this, but I am planning to do a large rewrite of the cache_storage backend in the next few months. This code will likely change as a result of that rewrite. So while I'd be happy to see you contribute to the project, I worry that any effort on this bug would end up being wasted in the relatively near term.
,
Sep 17
Thank you so much for your concern. I understand and should find another issue. |
|
►
Sign in to add a comment |
|
Comment 1 by pwnall@chromium.org
, Aug 18