Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I heard that .NET 4 has a new caching API.
Okay, so the good old System.Web.Caching.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.