ASP.Net Application State

HTTP protocol is a stateless protocol which does not help to maintain the state of the page for example when a request is sent to server by client an instance of the page is created and when the server respondes the instance and the value of control(s) is destroyed, there many techniques to maintain the state of the page one of them is Application state
Application state provides info based on application scope, this info is visible and could be used throughout the application. The info is stored in application state and this info is maintained by the server.
An example is when multiple sessions share the data which does not change is the best type of data to use through application state. It is very easy to use because only one copy of the info is good enough to share between multiple pages.
But on the hand it is highly recommended not to store unique values in application state because this will be global to only particular process and each process may have different unique values.

State management is an art which retains user specific info between requests but most of the time the scope of info is global to entire app, To achieve the goal of state management in the app you may mix up the following server-side state management options

For further question please mail: brainstormiert@gmail.com