Question - Define state management in ASP.NET.
Answer - State management is implemented
in order to retain information about the user requests. Web pages are
stateless. Each request creates new page without retaining any previous
information about the user requests. ASP.NET supports several State management
techniques to maintain state information.
State management in ASP.NET can be classified into
Client-side state management
Server-side state management
Question - Define each mechanism of Client-side state
management and Server-side state management.
Answer - Client-side state management
This maintains information on the client's machine using Cookies, View State,
and Query Strings.
Cookies.
A cookie is a small text file on the client machine either in the client's file
system or memory of client browser session. Cookies are not good for sensitive
data. Moreover, Cookies can be disabled on the browser. Thus, you can't rely on
cookies for state management.
View State
Each page and each control on the page has View State property. This property
allows automatic retention of page and controls state between each trip to
server. This means control value is maintained between page postbacks.
Viewstate is implemented using _VIEWSTATE, a hidden form field which gets
created automatically on each page. You can't transmit data to other page using
view state.
Querystring
Querystring can maintain limited state information. Data can be passed from one
page to another with the URL but you can send limited size of data with the
URL. Most browsers allow a limit of 255 characters on URL length.
Server-side state management
This kind of mechanism retains state in the server.
Application State
The data stored in an application object can be shared by all the sessions
of the application. The application object stores data in the key value pair.
Session State
Session state stores session-specific information and the information is
visible within the session only. ASP.NET creates unique sessionId for each
session of the application. SessionIDs are maintained either by an HTTP cookie
or a modified URL, as set in the application's configuration settings. By
default, SessionID values are stored in a cookie.
Database
Database can be used to store large state information. Database support is used
in combination with cookies or session state.
<<Previous
Next>>
Define Session, SessionId and Session State in ASP.NET.
What is
Session Identifier?
Advantages
and disadvantages of using Session State Management.
What
are the Session State Modes? Define each Session State mode supported by
ASP.NET.
Define Exception handling in ASP.NET. | What are the ways of
handling exceptions in ASP.NET? | Explain Try/catch block method of exception
handling. | Define Error Events. Define Custom Error Pages. | Why is exception
handling important to an application? | When can you use tracing with exception
handling?
What is Master Page in ASP.NET? | Advantages of using Master Page in ASP.NET |
Define Multiple Master Page. | How do you create Master Page?
|