Why aren't you using System.Web.Caching.Cache?  That way you can control the latency.

Good article...It's nice to see some C# code for a change.  this works well for small amounts of data (like lookup lists), as storing to much data in memory can seriously degrade performance.

When dealing with larger recordsets it's a good idea to cache to disk instead of memory.  The easiest way to do this in C# is using disconnected recordsets.  Basically, the data is serialized to disk as a XML recordset.

Of course, dealing with updates to data is an added layer of complexity, but this is a problem with any caching technique.  There are tons of solutions to this problem, though...they just take time to develop.

cl

Hi Malcolm,

Yes, you can use Cache instead of Session/Application. All store your live reference but Session with StateServer and SQL Server.  Have a look on this http://west-wind.com/weblog/posts/1214.aspx. This speaks about the way of storing objects by ASP.net with Cache and Session.

Dinesh