We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
fly.cache
This would mean moving most of this logic into the v8env: https://github.com/superfly/fly/blob/master/src/bridge/cache.ts
And just making calls to fly.cache from there. I think it would work well, provided the http-cache-semantics npm isn't overly complex.
http-cache-semantics
The text was updated successfully, but these errors were encountered:
I'm fine with that
Sorry, something went wrong.
Change cache.match/put/add to use fly.cache under the covers (fixes #1)
3212e19
a07d84c
3804d65
No branches or pull requests
This would mean moving most of this logic into the v8env: https://github.com/superfly/fly/blob/master/src/bridge/cache.ts
And just making calls to
fly.cache
from there. I think it would work well, provided thehttp-cache-semantics
npm isn't overly complex.The text was updated successfully, but these errors were encountered: