If I were to use AppState
variables as opposed to Session
variables, I would not be storing data user-specifically. That is, if one user changes an AppState
variable, it remains changed for all users on a site (it is application specific).
My question is, if I store values using the cache to transfer data between asp.net web-pages, is it user-specific or application specific? I always assumed it would be user-specific, however I read this:
The Cache is primarily intended to be used to improve performance of web pages, in that you can add any arbitrary object to it and retrieve it at will. Cache items are stored in memory on the server, and can be considered as special global variables.
(This is from: http://www.mikesdotnetting.com/Article/192/Transferring-Data-Between-ASP.NET-Web-Pages)
Knowing that the actual values are stored on the server, I began to wonder if the reference to these values are stored client side (like with Session variables) or if they are 100% stored server-side.
I would test this myself, but my work environment isn't really suitable for me to 'hop' on different machines very easily.