-
Notifications
You must be signed in to change notification settings - Fork 325
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
Go deeper into HTTP caching #373
Comments
Yeah, that aligns with my tentative plan for the cache. Either something like "HTTP-cache fetch" or a new Infrastructure subsection. Streams is still being improved and uploads isn't done yet. We can probably find some temporary wording though if it's required anywhere and we lack something. |
Am starting in https://github.com/mnot/fetch/tree/http-cache -- not done yet, but would love any feedback you have so far. |
One thing that would be good to take into account is #307. Effectively a browser needs at least two global instances of an HTTP cache, as defense-in-depth for CORS. That's why I was considering having the cache lookup be in its own section. I have editorial quibbles, but maybe those are better to do once you're ready? |
My first inclination is to break out some parts of HTTP-network-or-cache Fetch into new sections and then grow them.
Specifically -
If that makes sense, I'll start a branch, and probably some tests too.
Question - Is the Streams work largely done? I suspect some of the fine points here are going to need them.
The text was updated successfully, but these errors were encountered: