ASP.NET Whidbey Caching Overview
page 1 of 3
Published: 27 Oct 2003
Unedited - Community Contributed
Abstract
An overview of the new features in the ASP.NET Caching engine coming in ASP.NET v2 (whidbey).
by Steven Smith
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 28144/ 45

Caching in 1.x...

ASP.NET Caching in 1.x is very powerful and includes three pieces: output caching, fragment caching, and the cache API.  The simplest form, output caching, simply caches the output of a page.  Fragment caching is a bit more granular, and caches the output of a user control.  Finally, the most powerful caching functionality is achieved using the cache API, and allows any serializable object to be cached.  These cached items can then be invalidated based on a certain amount of time, a file or folder dependency, or another cached item.  There's also a cached item removed callback function that lets you execute some code after something as been removed from the cache.  For more on caching in 1.x, check out this MSDN article:

ASP.NET Caching Techniques and Best Practices (by Steve Smith)


View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2017 ASPAlliance.com  |  Page Processed at 2017-05-29 1:11:31 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search