-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You can "modify" entries in the cache api #2
Comments
Oh great! I don't understand how I missed that. I'll make this change, but now I need to find a way to store the version number. IndexedDB was interesting for this! |
You could put metadata in headers, but it could be that indexeddb is a better fit. |
I like the idea of storing the info inside the headers. A unique request to Cache is better than 2 requests to Cache + IDB. |
It may be good to update the part of the readme that talks about IDB to mention this Maybe just referencing this issue to say it's a possible work-in-progress. Otherwise folks may get the wrong idea about how the Cache API works |
Done. |
In cache storage, the requests & responses can be mismatched in terms of their original fetching, or either/both can be of your own making.
The text was updated successfully, but these errors were encountered: