[w3c/ServiceWorker] Remove incumbent/fetching record from Cache behavior (#1190)

This change removes the incumbent/fetching record concept that allowed
committing a fetching resource to cache and match/matchAll to return a
fully written existing resource, if any, with priority over a fetching
resource. After this change, add/addAll/put promises resolve when the
resources ared fully fetched and committed to cache. match/matchAll will
not return any on-going fetching resources.

This changes the specification type of underlying cache objects from a
map (request to response map) to a list (request response list). The
change is to make the arguments and the return values of the Cache
methods and algorithms (Batch Cache Operations and Query Cache) conform
to one another. The list type seems fine as the algorithms tend to
iterate through the list to find certain items with search options.
Looking at the details of the acutal implementations, I plan to update
it further if needed.

Fixes #884.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/ServiceWorker/pull/1190

-- Commit Summary --

  * Remove incumbent/fetching record from Cache behavior

-- File Changes --

    M docs/index.bs (205)
    M docs/index.html (5777)
    M docs/v1/index.bs (205)
    M docs/v1/index.html (4986)

-- Patch Links --

https://github.com/w3c/ServiceWorker/pull/1190.patch
https://github.com/w3c/ServiceWorker/pull/1190.diff

-- 
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/1190