The following are the commonly used state management techniques.
QueryString
Cookies
Cache
ViewState
Session state(eg: Session[“name”])
Application state
Static variables
Profiles
Are session state (e.g. Session [“name”]) and session management the same?
InProc, State Server and SQLServer mode: are these related to session state or session management?
State management and session management in ASP.NET are the same or not?
state management and session management are different, state management is made with viewstate, by default Web is stateless, but with Viewstate you can save data when you post, it's also used in order persist data with minimal code. for example for persisting dropdownlist you don't need bind data every time tou post.
but session is made with Session property of your context. she can be stored on your process, or on server hosted or in sql server.
Cache and Application are global cache in order share datas between differents sessions.
Cookies it's stored on your client
Profiles is dedicated for security need
Client-side state management: In some scenarios, it reduces network traffic and/or simplifies your client application, because you are not doing roundtrips Generally, you can store less data than if you used the server side approach You have less control over the integrity and consistency of the state, due to the environment where you're saving it (the client) State is confined to a computer, cannot follow the user Server-side: Needs roundtrips to the server and the complexities that come with those You have more control: what, where, how long you keep it Can follow the user accross system boundaries You have to decide what's better for your situation.
Web is Stateless. It means a new instance of the web page class is re-created each time the page is posted to the server. As we all know HTTP is a stateless protocol, its can't holds the client information on page. As for example , if we enter a text and client on submit button, text does not appear after post back , only because of page is recreated on its round trip.
As given in above pages, page is recreated before its comes to clients and happened for each and every request. So it is a big issue to maintain the state of the page and information for a web application. That is the reason to start concept of State Management. To overcome this problem ASP.NET 2.0 Provides some features like View State, Cookies, Session, Application objects etc. to manage the state of page.
http://www.codeproject.com/Articles/31344/Beginner-s-Guide-To-View-State
