Commit bedfb0d9 authored by Rayan Kanso's avatar Rayan Kanso Committed by Commit Bot

[Background Fetch] Add Cache Storage changes to README

Done using the "Edit in Gerrit" option in codesearch

Change-Id: I3a04b97abfcd67fb5d4a3eaa93f289341cb22f23
Reviewed-on: https://chromium-review.googlesource.com/1126142
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: default avatarPeter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572565}
parent f44c69ed
......@@ -45,6 +45,19 @@ key: "bgfetch_completed_request_<unique_id>_<request_index>"
value: "<serialized content::proto::BackgroundFetchCompletedRequest>"
```
## Cache Storage UserData schema
The downloaded responses of every fetch will be stored in their own private cache.
### Cache identifiers
* `origin`: `<origin>`
* `owner`: `CacheStorageOwner::kBackgroundFetch`
* `cache_name`: `<unique_id>`
The cache will contain all the Request/Response key/value pairs of the fetch.
Note that the Request value stored isn't comprehensive, and only the url value is
used to as a key to find the matching Response.
### Expansions
* `<unique_id>` is a GUID (v4) that identifies a background fetch registration.
E.g. `17467386-60b4-4c5b-b66c-aabf793fd39b`
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment