All session variables are stored in RAM, but using session variables is OK.
The only thing to watch for is that you don't overload your server's
memory resources by loading memory intensive data into session variables.
i.e., if you load a 5MB dataset into a session variable ( an extreme example )
and you have 1,000 visitors to your website before your default session timeout
expires, don't be too surprised if you have server memory exhaustion problems.
Otherwise, go ahead and use them without worry.
Just make sure that the total RAM used by the session variables
doesn't exceed a reasonably low percentage of your server's memory resources.
If you do, your server will recycle the application's process at the configured memory limit.
Even then, you can cushion yourself if you use SQL Server
or State Server to store your session data.
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================
"senfo" <en**********@yahoo.comI-WANT-NO-SPAMwrote in message
news:eI**************@TK2MSFTNGP06.phx.gbl...
I've had multiple people tell me that I should avoid using session variables, wherever possible
and suggesting using cookies and context instead; however, nobody has been able to give me an
explanation as to why. I'm aware of the issue when using kernel cache in IIS 6.0
(http://support.microsoft.com/kb/917072), however, I'm not using output cache right now.
I greatly prefer session variables to cookies for security reasons, so this is really bothersome.
Can somebody please offer some insight?
Thank you in advance,
--
Sean