ASP.net page output caching?

Up vote 1 down vote favorite 1 share g+ share fb share tw.

In asp.net I can set the page output cache to store at the web server or at the browser level. I have a couple of questions regarding this If the page output cache is set to be stored at the browser level, will there still be a postback on refresh click? Why would I choose web server level page output caching over client caching?

Asp.net caching outputcache link|improve this question edited Jan 5 at 2:21RickNZ9,410724 asked Jan 5 at 0:58developer7471947 73% accept rate.

Yes. Caching a page at the browser (or in a proxy) does not prevent postbacks. For pages where you are generating the same content for many users.

The goal is improved server-side performance. Also, you wouldn't normally use server side caching alone; by default, enabling it on a page also enables client caching. You might use server-only caching in cases where you want to retain a higher level of control over when users see new content.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.