ASP.NET Caching with Web Stimulus

Cached Page Lifecycle

Web Stimulus creates an instance of the server page and checks cache invalidation rules for every data packet on the page. If all cached data packets are still valid the server returns the HTTP response with code 304 Not Modified. If some of the cached packets are updated then they are added to the response. The Web Stimulus client framework will then receives the response and process the page with a correct combination of cached and new data packets.

Web Stimulus cached page lifecycle. Click for larger image.

The web application gets multiple benefits from client-side caching such as reduced network traffic and partial server page processing, which avoids redundant access to the database.

Technology Highlights

All-Tiers Acceleration Tool. Web Stimulus is used to effectively resolve the performance bottlenecks of any ASP.NET application on all tiers. more...

Fewer Limitations. Web Stimulus removes many web application limitations and solved many web performance problems. more...

Page Lifecycle. Web Stimulus adds another dimension to the ASP.NET page lifecycle. It facilitates the page's second ASP.NET lifecycle on the client. more...

Page State. Web Stimulus raises web page statefulness to a new level. It automatically allows restoring not only the state of controls, but also the state of any other page member. more...

Cached Page Lifecycle. Web Stimulus maximizes page efficiency by assembling it on the client using valid cached page elements and elements downloaded from the server. more...

Optimizing ViewState. Web Stimulus completely removes ViewState from the download traffic and reduces its payload 3-5 times in the upload traffic. more...