Session VS. ViewState For Small Value

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Fred Newton (a_at_b.com)
Date: 08/06/04 

Date: Thu, 5 Aug 2004 22:33:04 -0700

Just wondering if there are any strong arguments one way or the other for
storing a small value (6 bytes) in the ViewState vs. Session state. The
value is needed in only one page in a large ASP.NET app. I'm interested in
knowing performance differences specifically and anything a beginning
ASP.NET developer might not be thinking about. FWIW: I'm *not* considering
the 3rd obvious option - cookies.

Thanks!

Relevant Pages

  • Re: Session VS. ViewState For Small Value
    ... ViewState is useful for storing ... If you use Session State, the value you insert will remain in memory ... I think after my explanation, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Session VS. ViewState For Small Value
    ... Session State is useful for storing values that must be persisted across ... serializable data that must be persisisted across PostBacks by a single ... ViewState, the value you insert will remain in ViewState until the user ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Storing a datatable in application or session state?
    ... I said session state but meant viewstate. ... >>> luck with session state rather than viewstate which is why I'm asking, ... I thought simply that one is for server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Storing a datatable in application or session state?
    ... I said session state but meant viewstate. ... would I have to serialize then deserialize the dataset? ... this can eat a lot of server memory if you have very ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: DataSets & DataAdapters
    ... >> because I have viewstate enabled on the textboxes that's storing the ... >> Now, if the user modify's the textboxes and hits the save button, I ... >> How do I get around this problem without persisting the DS in ...
    (microsoft.public.dotnet.languages.csharp)