Depends what you have there, however if you store something like controls
there, you're shooting yourself to leg for good. All those resources are
tied to the lifetime of a session, and it would be multiplicated per-user
basis.
I'd look into Caching as Juan hinted, depending on your case either data
caching with cache object or outout caching (caching the rendered content)
when you could avoid non-needed caching or cache only the necessary
resource-intensive part.
--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
"py" <du***********@hotmail.com> wrote in message
news:u$**************@tk2msftngp13.phx.gbl...
how feasible is it to cache an entire page's content in a session
variable?
i am already doing it and it works fine, except i am afraid of scalability
issues. what is the best way to test this? and is there an obvious
reason
why i should not do this.