Thread: Caching
View Single Post
  #1 (permalink)  
Old May 27th, 2010, 06:55 PM
chroniclemaster1 chroniclemaster1 is offline
Friend of Wrox
Points: 1,749, Level: 16
Points: 1,749, Level: 16 Points: 1,749, Level: 16 Points: 1,749, Level: 16
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jun 2007
Location: San Diego, CA, USA.
Posts: 477
Thanks: 10
Thanked 19 Times in 18 Posts
Default Caching

Based on the page life cycle, all the application code which runs from the App_Code folder is destroyed at the end of a request correct?

Yet I've seen people use caching that only seemed to make sense if it was going to persist from one page request to another (including different Wrox books, among other places). How is this accomplished?

I sold on the desirability of storing important information in the application so you don't have to keep looking it up in a web service or DB, but I don't understand how a custom cache object survives the end of the page request without storing it in an external resource (which kinda defeats the purpose).

Whatever you can do or dream you can, begin it. Boldness has genius, power and magic in it. Begin it now.
-Johann von Goethe

When Two Hearts Race... Both Win.
-Dove Chocolate Wrapper

Chroniclemaster1, Founder of
A Growing History of our Planet, by our Planet, for our Planet.