On page 205 in the table under Page Request. It reads as follows... A request to an APSX page starts the life cycle of that page. When the web server is able and allowed to return a cached copy of that page, then the entire life cycle is not executed. In all other situations, the page enters the start phase.

Could someone please elaborate on the sentence where it says ---When the web server is able and allowed to return a cached copy of that page, then the entire life cycle is not executed.

What is a cached copy? Why is the entire page life cycle not executed in this situation? When would I want to use a cached copy? And when would I not want to use one?

Thanks for any help in understanding this in a little more depth.

Hi there,

A cached page is a copy of a final page that is stored for quick retrieval later.

Caching is mostly useful when a) it's expensive to build the page (look up stuff from a database for example) and b) the page contents are relatively static (since the page is cached for the entire server, it's difficult to store user specific data).

The first time a cachable page is requested, its output is stored and returned on subsequent requests; hence the lack of the life cycle. You can store specific versions of a page based on parameters. For example, Product.aspx?Id=23 that shows product 23 can have its own copy, just as Product.aspx?Id=345

For more information:

http://msdn.microsoft.com/en-us/library/hdxfb6cy.aspx
http://www.google.com/#hl=en&source=...10401dfb0a78c2

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!