-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Open
Labels
area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresfeature-cachingIncludes: StackExchangeRedis and SqlServer distributed cachesIncludes: StackExchangeRedis and SqlServer distributed caches
Description
Are there any plans to implement a sliding expiration for HybridCacheEntryOptions
?
The existing DistributedCacheEntryOptions
has a SlidingExpiration
property which has been working well for my team and I. We have another mechanism to invalidate cache keys when updates to the underlying data occurs so we like to keep the data in Redis for as long as it is being used and eventually expire when that particular data is not regularly accessed.
Desired Solution
Ideally, the same SlidingExpiration
property would be added to HybridCacheEntryOptions
and the value would be passed along in ToDistributedCacheEntryOptions
and handled in the downstream IDistributedCache
calls
AinoraZ, Uxeron, smorton-planview, leandrobattochio, bastien-oc and 17 more
Metadata
Metadata
Assignees
Labels
area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresfeature-cachingIncludes: StackExchangeRedis and SqlServer distributed cachesIncludes: StackExchangeRedis and SqlServer distributed caches