Whenever the client sends a request for the first time then ASP>Net will process the request and the result will be maintained as a cached content such that for further clients request the response will be provided from the cache.
- Whenever the cached content is maintained on a Web server then it is said to be ServerSide caching.
- Whenever the cached content is maintained on the client System then it is said to be client-side caching.
- Net set client-side cache content implicitly for all web forms.
- In order to kill the cached content at the client system then “Response.Express = -1;” should be used.
Inclined to build a profession as VB.Net Developer? Then here is the blog post on, explore VB.Net Training
Whenever the cached content is maintained at a web server then it is said to be server-side caching.
ASP.Net supports the following server-side cache concepts:
- Page output cache
- Page fragmentation cache
- Substitution cache
- Data cache
- Output caching [ASP.Net 4.0]
Page Output Cache:
Whenever the client sends a request for the first time then the entire page output will be maintained as cache content such that for further client's request without processing the response will be provided from the cache. To set: [In ASPX page] < % @ Output cache Duration = “Seconds” varyBy Param = “ Control Name|Variable | none” . . .% >
For an in-depth knowledge, click on below