expiration_time & should_cache by key
In a use case, some of the data is hot data(recent and changes a lot) and some is cold data(almost never change).
So it would be great if I can use a a function to dynamic set expiration time by key. For cold data use a very long expiration time while hot data less.
And the same goes for should_cache_fn, I don't want cache for the real time hot data, while cold data can be cached for a long time.
How do you think about it?