Add the EntryOption => MemoryCacheDuration

[emeesterinterpulse]

At the moment we work with sliding Expirations on System.Runtime.MemoryCache. (Basicly to To keep memory Low). We looking into a migration to FusionCache (no that tagging is supported). We implemented ImemoryCache on System.Runtime.MemoryCache. So we can easly map Duration to SlidingDuration.

But the problem is that we want the cache LogicalDuration 24 hours (or unlimited, we invalidate cache pure on Tags. ) But we want to keep the sliding expire time low, lets say 20 minutes.

So an extra option MemoryCacheDuration like DistributedCacheDuration could help in our situation.

I also Followed the SlidingExpiration discussion. Maybe our case is one to consider for adding a sliding expiration to fusionCache. (Memory cache only, if it's important data we store it also in de L2 cache)

[jodydonetti]

Hi @emeesterinterpulse sorry, super late here: after the mega crunch to release v2, helping the DAB team to introduce L2+backplane, my daily job and life in general I got carried away, my bad.

Regarding a new MemoryCacheDuration option: truth be told, I've already worked on it right before v2 landed, I wanted to include it directly there but did not have the time to cover all possible scenarios, edge cases and features combination (eg: fail-safe + eager refresh + different memory/distributed durations + etc).

Anyway, it's definitely on my list of features to add to FusionCache: apart from some technical complexities, the only thing I'm trying to figure out is how to best communicate what does Duration do when there is a different MemoryCacheDuration and a DistributedCacheDuration at play, I'd like the message to be clear and consistent.

Any thoughts on that would be more than welcome.

Thanks!

[jodydonetti]

Hi @emeesterinterpulse , see here.
Long story short: it's coming in the next version, coming out ideally tonight!