Using output caching caches the HTML for the page on the server and uses that
HTML for subsequent requests, rather than regenerating the code for each one.
This is why your users are seeing each other's data.
There are several other options and without more info about your app I can't
tell you which will work for you.
VaryByParam: If you are using paramters in the URL then you can use the
VaryByParam property with output cahching to store different versions of the
HTML based on the values of the parameter in the URL.
Partial Caching: If you want to cache only parts of the page and keep others
dynamic look into partial page or fragment caching.
Data Caching: This may be what you are looking for. You can cache the data
(DataSets, DataTables, etc) that you are using in your application. For
instance, you can cache a dataset then create a view for each user based on
thier selections.
There is a lot information about these options if you do some searching.
Hope this helps
"BillGatesFan" wrote:
I'm trying to understand ASP.NET caching. I set the Page Output
directive to VaryByParams= None and the duration = 60.
Now whenever users hit my web app they can see each others data. Is
there anyway to cache the page without this happening or am I using
Page Output caching in the wrong situation?
It's a data entry web app that I'm trying to increase the performance
on.