Hi

@Brin351:
I'm not saying you can abuse sessions, even when you have your own server with good hardware, of course that you still need to know what you're doing, calculate the amount of memory your sessions will consume (as much as you can) this is what I did and it's working much better then my expectations.

and here is a quote from microsoft article that you posted above:

Code:
Session-state variables that contain blocks of information, such as large datasets, can adversely affect Web-server performance as server load increases
just as I wrote earlier, do NOT save large tables or data in sessions but general information such as user preference and other basic data which otherwise you'll have to connect to your database almost in every page you should save in sessions or the built in ASP.NET feature member profile (which I didn't had the chance to use yet)

@techgnome
you aware that we're talking about sessions and not viewstate right?

I dislike the ASP.NET viewstate feature as well and very rarely you'll find it not disabled in my web projects pages.