ASP.NET Caching

From Visual Studio Magazine, March 5, 2002

• system level (runtime provided) caching, persisting compiled pages on a per-application basis
  
• application level, persisting output of static pages
  
• page level, access to new Cache object that works side-by-side with Session and Application (see "tidbits" below)
  

   <%@ OutputCache

   Duration="seconds"

   Location="where"

   VaryByCustom="custom"

   VaryByHeader="headers"

   VaryByParam="paramname"

   %>

5 Vital Caching Tips


Cache and Carry With ASP.NET (Dino Espisito)

A couple more caching tidbits

• Store cache expiration settings in a centralized place. Instead of DB, try writing an "application settings" object that persists itself to xml on disk. Can reload the settings from disk whenever you want (from admin page, or from the code detecting a change in the file timestamp)
  
• Cache object is thread-safe from any page with Insert and Item methods, while the Application object must be wrapped with calls to Lock/Unlock
  
• Cache object has timeout settings when the data you insert will be thrown away
  
• Can "listen" for cache item expirations with CacheItemRemovedCallback delegate