Output-cache providers can use any storage mechanism to persist HTML content.This makes it possible to create custom output-cache providers for diverse persistence mechanisms, which can include local or remote disks, cloud storage, and distributed cache engines.
NET 1.0 was released, output caching has enabled developers to store the generated output of pages, controls, and HTTP responses in memory. NET can serve content more quickly by retrieving the generated output from memory instead of regenerating the output from scratch.
However, this approach has a limitation — generated content always has to be stored in memory, and on servers that are experiencing heavy traffic, the memory consumed by output caching can compete with memory demands from other portions of a Web application. NET 4 adds an extensibility point to output caching that enables you to configure one or more custom output-cache providers.
Contents Core Services Web.config File Refactoring Extensible Output Caching Auto-Start Web Applications Permanently Redirecting a Page Shrinking Session State Expanding the Range of Allowable URLs Extensible Request Validation Object Caching and Object Caching Extensibility Extensible HTML, URL, and HTTP Header Encoding Performance Monitoring for Individual Applications in a Single Worker Process Multi-Targeting Ajax j Query Included with Web Forms and MVC Content Delivery Network Support Script Manager Explicit Scripts Web Forms Setting Meta Tags with the Page. Meta Description Properties Enabling View State for Individual Controls Changes to Browser Capabilities Routing in ASP.
NET 4 Setting Client IDs Persisting Row Selection in Data Controls ASP.
Some Web applications need to load large amounts of data or perform expensive initialization processing before serving the first request. NET, for these situations you had to devise custom approaches to "wake up" an ASP.