You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
I am using cacache with make-fetch-happen to cache fetch responses from a forecast API. These responses are pretty big (~60 kB) and differ every hour.
What worries me a little bit is the fact that stale responses are kept by default. I expected the stale response to be replaced by the fresh one if the key matches.
I've investigated the documentation thoroughly and the closest thing I've found is calling rm.content just before putting new one.
Is this the right thing to do?
Have I overlooked something?
What is the reason for keeping stale responses by default?
Is purging stale responses out of the scope of this library?
If this is generally accepted cache behavior, can you please point me to some explanation?
Thank you.
The text was updated successfully, but these errors were encountered:
I am using cacache with make-fetch-happen to cache fetch responses from a forecast API. These responses are pretty big (~60 kB) and differ every hour.
What worries me a little bit is the fact that stale responses are kept by default. I expected the stale response to be replaced by the fresh one if the key matches.
I've investigated the documentation thoroughly and the closest thing I've found is calling
rm.content
just beforeput
ting new one.Is this the right thing to do?
Have I overlooked something?
What is the reason for keeping stale responses by default?
Is purging stale responses out of the scope of this library?
If this is generally accepted cache behavior, can you please point me to some explanation?
Thank you.
The text was updated successfully, but these errors were encountered: