I keep mulling over the best cache expiration policy for my particular application. It's a Windows Form data entry program and I was looking at caching the data that I use to populate my combo-boxes. That data is probably the most static and frequently
accessed. It seems to me that a notification-based expiration would be the best approach to determine the validity of this cached data. I would not have to invalidate the cache unless someone went in and added a record to the table I'm caching.
1) Does the scenario above sound like a normal caching scenario? I'm still trying to get my head wrapped around whether I should be caching data or not.
2) I've seen some references to Ron Howard's team page on GotDotNet, but it's not there anymore. Does anyone know where I might find the contents now?