State Management in ASP.NET

.NET Development

The following notes were taken during a lecture in COMP 241 .NET Web Applications at Camosun College by Rob Thorndyke.  These notes are here mainly to help me study, but if you can find some guidance through them then all the better!

Client side State Management

  • Scalable
    • As # users grows, server space doesn’t
  • Easy to add web servers
  • Ways to do it in .NET:
    • Hidden Fields
    • Cookies
    • Query Strings
    • ViewState -> fancy hidden field (hashed values/objects)
    • **Control State – just checking state of control.

Server side State Management

  • Secure
  • Bandwidth is lower
    • (eg Mobile devices)
  • Variables in .NET:
    • Application – global to all users (use Lock() and Unlock())
    • Session – global to each user (uses Cookies to store SessionID())
      • Configure in Web.Config to use “cookieless sessions” -> ID is sent via Query String
Bookmark and Share
1 Comment

One Response

  1. Dan  •  October 24, 2008 @12:00 am

    Didn’t understand a word.
    You are the literal definition of a genius.

Leave a Reply

Allowed tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">