I am not sure if I am heading in the right direction.

I have a list which is used very frequently and I want to cache it for performance reasons.

DotNetNuke.Services.Cache.CachingProvider.Instance().Insert("MyList", object, true);

With the above statement, can I expect "MyList" to survive app restart(which means, if app restarts, I dont have to query it from the database?)

and does this list expire (removed from cache) in a specified time?

How do I make it to stay in the cache forever?

Please let me know..

TIA

In general you let the host decide what the lifetime in the cache should be, so it is considered 'rude' to override others by plugging in the cache and telling the caching engine: "hey I'm real important, you got to keep me forever". Instead you take the parameters as set by the host as a basis for caching. The pattern most often used in DNN is as follows:

• You make a method along the lines of GetMyList()
• You set a variable to what you need to return and set it to null
• Attempt to retrieve from the caching engine the cached value
• IF the return var is still null, construct it and add it to the cache using your rule
• Return the var

This is a very robust and friendly way to handle caching in DNN. Remember there are potentially other developers 'next to you' (i.e. other modules) that also use the cache. Sticking to 'best practice' ensures that the end users get the best performance from the framework as the DNN core developers assume this is what you do.

My 2cts on this ...

I agree Peter..I have some of my lists loaded this way..I check if its in cache, if not, add it to cache and use it..but I was trying to avoid doing that also as my lists wont change really..