Session VS. ViewState For Small Value

[Fred Newton]

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!

[Kevin Spencer]

Session State is useful for storing values that must be persisted across
multiple pages by the same user. ViewState is useful for storing
serializable data that must be persisisted across PostBacks by a single
page. If you use Session State, the value you insert will remain in memory
until (1) The Session times out, or (2) Your code removes it. If you use
ViewState, the value you insert will remain in ViewState until the user
requests a different page.

ViewState stores data betwen PostBacks by putting it into a hidden form
field on the client HTML doc. when the doc is Posted Back, the values are
read from the hidden form field and stored in memory until the page has
finished processing. If ViewState is particularly large (and I'm talking KBs
here, not 6 bytes), it can negatively affect the speed at which the HTML doc
is downloaded by the browser.

Use the right tool for your job. I think after my explanation, it should be
obvious that you would want to use ViewState in your specific case.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Fred Newton" <[e-mail]> wrote in message
news:OH**************@TK2MSFTNGP10.phx.gbl...

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!

[Fred Newton]

<< I think after my explanation... >>
Perfectly clear - thanks!
"Kevin Spencer" <ks******@takempis.com> wrote in message
news:O3*************@tk2msftngp13.phx.gbl...

Session State is useful for storing values that must be persisted across
multiple pages by the same user. ViewState is useful for storing
serializable data that must be persisisted across PostBacks by a single
page. If you use Session State, the value you insert will remain in memory
until (1) The Session times out, or (2) Your code removes it. If you use
ViewState, the value you insert will remain in ViewState until the user
requests a different page.

ViewState stores data betwen PostBacks by putting it into a hidden form
field on the client HTML doc. when the doc is Posted Back, the values are
read from the hidden form field and stored in memory until the page has
finished processing. If ViewState is particularly large (and I'm talking KBs here, not 6 bytes), it can negatively affect the speed at which the HTML doc is downloaded by the browser.

Use the right tool for your job. I think after my explanation, it should be obvious that you would want to use ViewState in your specific case.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Fred Newton" <[e-mail]> wrote in message
news:OH**************@TK2MSFTNGP10.phx.gbl...

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!