|
ASP.NET Book
The online ASP.NET Tutorial Book |
|||||||||
|
|
|||||||||
ASP.NET BasicsHTML BasicsASP.NET Web Server Advanced HTML Application Designing Using Visual Studio ASP.NET Standards ASP.NET Styling ASP.NET Navigation ASP.NET TipsASP.NET ValidationHTML forms CSS Styling CSS Advanced ASP.NET Features ASP.NET Image Effects Common mistakes DB Design tips Building ApplicationsDesign Secure AppsBuild Secure Apps |
3.2 Caching Content |
||||||||
|
If no caching mechanism was used, the traditional way an ASP.NET page is brought to the requesting browser as the following. For example: Let’s say a user requested an ASP.NET page with complicated charts, graphs, videos, images. Then what happens is the data needed to create these components comes from a SQL Server database. This database then executes the data through various queries. After this is done, the HTML, images, videos and any other JavaScript are then assembled and transferred through the internet to the user’s browser and the process is completed. Now let’s say another user requested the same ASP.NET web page. Then the whole process has to be repeated to provide the same output, and this is said to be expensive for the server, as it repeats the same process over and over again. So to avoid this hassle, and to reduce the server load, the only solution is to store a copy of these complicated and lengthy diagrams, images, reports or the web page itself, also known as expensive content, in the server’s memory. So on the next request, the Web server looks for that content in the cache and if it finds the web page, it sends copy of the cached page. The following ASP.NET tutorial helps you learn some of the significant of using cache for your web pages and web sites. Table of ContentsChapter 1 - HTML Web Standards [top] |
|||||||||