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
As the title indicates, I have a need for the wrapped method to define the cache refresh time of the data that is being returned.
If I make an http call to get a config item that rarely changes - the server might respond with the header: Cache-Control: MAX-AGE=900. so now I want to cache that data for 900 seconds, but if the code of the server changes to respond with Cache-Control: MAX-AGE=1500. I don;t want to change my code I want it to adapt to the new cache-control header.
There may be other patterns in which this type of caching could be used.
Do you have a method to handle this if not I have a rough POC of a change to your wrapper that could work that I'd be willing to provide if you are interested.
The text was updated successfully, but these errors were encountered:
…e/update time control (different settings per entry).
* Minor fix for contribution guide (after migration, Travis was still mentioned instead of GitHub Actions).
…e/update time control (different settings per entry). (#26)
* Minor fix for contribution guide (after migration, Travis was still mentioned instead of GitHub Actions).
As the title indicates, I have a need for the wrapped method to define the cache refresh time of the data that is being returned.
If I make an http call to get a config item that rarely changes - the server might respond with the header:
Cache-Control: MAX-AGE=900
. so now I want to cache that data for 900 seconds, but if the code of the server changes to respond withCache-Control: MAX-AGE=1500
. I don;t want to change my code I want it to adapt to the new cache-control header.There may be other patterns in which this type of caching could be used.
Do you have a method to handle this if not I have a rough POC of a change to your wrapper that could work that I'd be willing to provide if you are interested.
The text was updated successfully, but these errors were encountered: