I am a little biased after seeing page sizes of 500K+ that was killing VPN users drop to under 50K. ViewState and Session can both be abused.
I have seen a lot of people putting DB connection OBJECTS in session. This was with the SQL Server provider that supports connection pooling. So, no reason or speed advantage to stick a db connection object into session. So I do agree that abuse of Session is more rampant. Though I have seen that abuse of ViewState can kill performance much more than Session abuse, especially over a VPN connection. > IMHO, Serializing to ViewState is always better than to Session. Oh no, the gloves are coming off ;-) On Sun, Apr 12, 2009 at 3:40 AM, Cerebrus <[email protected]> wrote: > > I do not necessarily agree with that interpretation, Astro. I find > that abuse of Session state is much more rampant than abuse of > ViewState. ViewState is a very good option when you need to persist > state for a single page. But like any good method, abuse/overuse is > always a bad thing. > > In this case, I think serializing the Employee object to ViewState is > not a bad option. IMHO, Serializing to ViewState is always better than > to Session. > > On Apr 12, 8:46 am, AstroDrabb <[email protected]> wrote: >> ViewState ABUSE!!!
