State Management

Hi,

The HTTP is stateful mechanism even though it can't maintain the state of the controls across the post back to the server. It needs some mechanism to maintain the state of the web page even post backs.

Session can be maintained in client and server

1) Client:

- Cookies

- Hidden Fields

- Query string

- View state

- Control state

2) Server:

- Session state

- Application state

- Database

The server state mechanism:

Session state:

The session state is server side state management mechanism. There are three types of session state

1) InProc

2) OutProc

3) Sql Server

InProc is default session state management, it will store the session in the processor memory (IIS). The aspnet_wp.exe will have the store mechanism to maintain the state of the session. when every you restart the IIS the session will be expired.

OutProc is another session state mode, it will store the session on the aspnet_state.exe, it can be local or remote where multiple application can share the same session.

SqlServer is store the session on the database table, where it needs serialization and deserialization every retrieve and store.

Application state:
The application state is global state variable, where all the users can share the value in the application variable.
It has the key and value pairs.

Application["Version"] = "1.2";

Client side state management:

- Cookies
it is client side, it is not safest way because some body can view or disable in the client browser. It is small state management, it will be stored on the client browser. The user name and password can be stored.

- Hidden Fields
It will be stored in the client side hidden control and persists across the post backs.

- Query string
It has the limitation to have in the url (0to2550 and it can be part of the url to pass the value between the pages.

- View state
The view state is client side and every control will have the option to store the state of the control through the view state because it will store the encrypted value of the control state in the hidden control.

- Control state

Hope this will help you.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Satyapriya Nayak14y ago
Hi Arun,

Please refer the below links

http://www.c-sharpcorner.com/uploadfile/nipuntomar/state-management-in-Asp-Net/default.aspx

http://www.c-sharpcorner.com/uploadfile/meetuchoudhary/state-management-in-Asp-Net/default.aspx

Thanks
0
Senthilkumar14y ago
Hi,

The HTTP is stateful mechanism even though it can't maintain the state of the controls across the post back to the server. It needs some mechanism to maintain the state of the web page even post backs.

Session can be maintained in client and server

1) Client:
- Cookies
- Hidden Fields
- Query string
- View state
- Control state

2) Server:
- Session state
- Application state
- Database

The server state mechanism:

Session state:
The session state is server side state management mechanism. There are three types of session state

1) InProc
2) OutProc
3) Sql Server

InProc is default session state management, it will store the session in the processor memory (IIS). The aspnet_wp.exe will have the store mechanism to maintain the state of the session. when every you restart the IIS the session will be expired.

OutProc is another session state mode, it will store the session on the aspnet_state.exe, it can be local or remote where multiple application can share the same session.

SqlServer is store the session on the database table, where it needs serialization and deserialization every retrieve and store.

Application state:
The application state is global state variable, where all the users can share the value in the application variable.
It has the key and value pairs.

Application["Version"] = "1.2";

Client side state management:

- Cookies
it is client side, it is not safest way because some body can view or disable in the client browser. It is small state management, it will be stored on the client browser. The user name and password can be stored.
- Hidden Fields
It will be stored in the client side hidden control and persists across the post backs.
- Query string
It has the limitation to have in the url (0to2550 and it can be part of the url to pass the value between the pages.
- View state
The view state is client side and every control will have the option to store the state of the control through the view state because it will store the encrypted value of the control state in the hidden control.
- Control state

Hope this will help you.
0
MuthuMari M14y ago
Hi,
pls refer this url

http://www.c-sharpcorner.com/uploadfile/meetuchoudhary/state-management-in-Asp-Net/

http://www.c-sharpcorner.com/uploadfile/37db1d/hour-1-understanding-5-Asp-Net-state-management-techniques-in-5-hours/

http://www.c-sharpcorner.com/UploadFile/ganesh.nataraj/ASPdotNETSessionState09212005235624PM/ASPdotNETSessionState.aspx

thanks,

If this post is useful then mark it as "Accepted Answer"
0