CacheList#match - make cache name optional?

[jakearchibald]

Storing stuff in multiple caches is great, but leads to fetches like…

this.onfetch = function(event) {
  event.respondWith(
    caches.match('whatever', event.request.url).catch(function() {
      return caches.match('somethingElse', event.request.url);
    }).catch(function() {
      return caches.match('foobar', event.request.url);
    }).catch(function() {
      return fetch(event.request);
    })
  );
};

…as we search through caches for one with a match. It's possible, but unlikely to have two caches containing the same url. It'd be nice to swap the params of match around and make the cache name optional.

this.onfetch = function(event) {
  event.respondWith(
    caches.match(event.request.url).catch(function() {
      return fetch(event.request);
    })
  );
};

Much shorter. If the url exists in two caches, just return one of them.

[annevk]

If we do this, please do define in detail which resource is returned in case of a duplicate match.

[jakearchibald]

Well, querySelector returns the first match, so match could return the first cached item?

[annevk]

Sure, but that means you have to define how the caches are ordered relative to each other.

[jakearchibald]

What order do items iterate in a map? Could use that.
On 2 Nov 2013 00:28, "Anne van Kesteren" notifications@github.com wrote:

Sure, but that means you have to define how the caches are ordered
relative to each other.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/117#issuecomment-27573731
.

[tabatkins]

Maps are iterated in insertion order. As long as these are always author-defined, we're fine. Can they ever get created by the browser?