How and when should I use CacheItemPriori ty.NotRemovable ?

[Michael]

Hi,
I wrote the code to test how CacheItemPriori ty.NotRemovable works:

Cache.Insert("T ime", DateTime.Now,
new System.Web.Cach ing.CacheDepend ency(Server.Map Path("Test.txt" )),
System.Web.Cach ing.Cache.NoAbs oluteExpiration ,
System.Web.Cach ing.Cache.NoSli dingExpiration,
CacheItemPriori ty.NotRemovable , null);

When then Test.txt is changed, the cache item "Time" is unavailable,
so CacheItemPriori ty.NotRemovable parameter is useless here?
How to use CacheItemPriori ty.NotRemovable and when should I use it?

Thanks!

[Karl Seguin]

I would advise against using it. Your basically telling .NET to do
everything it can to keep the item in the cache. Of course, if the file
changes, that'll take priority. The priority only takes effect when none of
your other conditions are met (dependency, expiration time) but .NET needs
to free up some memory. It'll go through all the Cache item and purge them
based on priority until the needed amount of data is freed.

If you really don't want something to be removed, store it in the
Application object. But I'd only do that, or use NotRemovable when it was a
small piece of data that took a very very long time to get.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"Michael" <hu**********@g mail.com> wrote in message
news:Oj******** *****@TK2MSFTNG P15.phx.gbl...

Hi,
I wrote the code to test how CacheItemPriori ty.NotRemovable works:

Cache.Insert("T ime", DateTime.Now,
new System.Web.Cach ing.CacheDepend ency(Server.Map Path("Test.txt" )),
System.Web.Cach ing.Cache.NoAbs oluteExpiration ,
System.Web.Cach ing.Cache.NoSli dingExpiration,
CacheItemPriori ty.NotRemovable , null);

When then Test.txt is changed, the cache item "Time" is unavailable,
so CacheItemPriori ty.NotRemovable parameter is useless here?
How to use CacheItemPriori ty.NotRemovable and when should I use it?

Thanks!

[Michael]

Hi Karl,

Got it! Thank you very much :)

I would advise against using it. Your basically telling .NET to do
everything it can to keep the item in the cache. Of course, if the file
changes, that'll take priority. The priority only takes effect when none
of your other conditions are met (dependency, expiration time) but .NET
needs to free up some memory. It'll go through all the Cache item and
purge them based on priority until the needed amount of data is freed.