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!!! > > ViewState should be used for controls, not as an alternative to a > session variable. > > I have seen too many corp. apps that use ViewState as Session and you > end up with > pages that are 200K+. > > ViewState gets sent with every request. So sticking something in > ViewState sends > it to the client and then the client sends it back, for every darn request. > > Use a Session if you want to save something that is not for a Control state. > > With a Session you only send a session id. > > I did this one contract for the govt. where they paid a boat-load of > money for some > consulting companies "framwork". This "framework" put freaking everything in > ViewState. Page sizes were always 500K+. I was brought on to "optimize" the > app. I basically had to go through the whole dang "framework" and just change > everything from ViewState to Session. Bang, ShamWow. Much faster. WAY > faster > over the VPN, and much higher concurrent user numbers. > > Don't abuse ViewState. Don't use it if you didn't make a custom control.- > Hide quoted text - > > - Show quoted text -
