title: ASP.NET Cache - Callback versus Refresh - How to decide?
body: <p>Does a callback put more strain on a server in terms of cpu because it has to watch for a change all the time?</p>
  
  <p>I suppose a refresh makes code a little less manageable in that you have to find the place where the cache is being refreshed and there might be a tendency to forget to add the refresh?</p>
  
  <p>When the cache is being refreshed, the page called will seem to load longer when cache is being refreshed, a callback, might be less noticeable?</p>
  
  <p>For refresh, it may not happen for awhile until a page is hit, so there is possibly stale data?  Page hit, change in data immediately after.</p>
  
  <p>Thoughts?  The above I wrote assume caching is done for data from a database.</p>