I heard that .NET 4 has a new caching API.
Okay, so the good old System.Web.Caching开发者_JS百科.Cache (which is, by the way, still there in .NET 4) has the ability to set so-called CacheDependency objects to determine whether a cached item is expired or not.
One can also specify custom logic for determining whether a cached item is still useable or not by deriving a custom subclass from CacheDependency.
I'm curious, is there a way to provide such a logic in the new API?
I haven't really used it yet but classes derived from ChangeMonitor Class appear to serve a similar purpose.
Using System.Web.Caching.Cache with a CacheDependency was constructed something like the following:
CacheDependency cacheDependency = new System.Web.Caching.CacheDependency(null, new string[] { "dependentOnThisKey" });
cacheInstance.Add("someCacheKey", new object(), cacheDependency);
With System.Runtime.Caching this moves into the CacheItemPolicy ChangeMonitors. The above example changes to the following:
CacheItemPolicy policy = new CacheItemPolicy();
policy.ChangeMonitors.Add(MemoryCache.Default.CreateCacheEntryChangeMonitor(new List<string> { "dependentOnThisKey" }));
cacheInstance.Add("someCacheKey", new object(), policy);
 
         
                                         
                                         
                                         
                                        ![Interactive visualization of a graph in python [closed]](https://www.devze.com/res/2023/04-10/09/92d32fe8c0d22fb96bd6f6e8b7d1f457.gif) 
                                         
                                         
                                         
                                         加载中,请稍侯......
 加载中,请稍侯......
      
精彩评论