ASP.NET State management
Upcoming SlideShare
Loading in...5
×
 

ASP.NET State management

on

  • 9,336 views

This PPT explains about the various ways to manage the state of an asp.net web application. This PPT is for complete beginners and intermediate developers who want to know few things about Asp.net ...

This PPT explains about the various ways to manage the state of an asp.net web application. This PPT is for complete beginners and intermediate developers who want to know few things about Asp.net State Management. Here I have explained in brief about the various techniques we use to manage the state of our application.

Statistics

Views

Total Views
9,336
Views on SlideShare
9,336
Embed Views
0

Actions

Likes
2
Downloads
255
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

ASP.NET State management ASP.NET State management Presentation Transcript

  •  Introduction of State Management Types of State Management  Client Side Techniques  Server Side Techniques Client Side State Management  (Introduction and Ways) Server Side State Management  (Introduction and Ways)
  •  Http is a stateless protocol. Web Server does not have any idea about the requests. Example – Online Registration Form
  •  Client Side State Management  Utilizes Clients Resources  Ways : View state, Hidden fields, Query string, Cookies Server Side State Management  Utilizes Server Resources  Ways : Session State, Application State.
  • Client Side State Management View State –  It stores information submitted through form and works between requests of the same page.  The values written in the server control is passed as a variable to an HTML hidden input field. Advantages 1. No Server resources required. 2. Simple Implementation Disadvantages 1. Performance Consideration 2. Potential Security risks
  •  Hidden Fields –  Can be used to store page specific information  Can be used to store small amount of data Advantages 1. No Server resources are required 2. Widespread Support 3. Simple Implementation Disadvantages 1. Performance Considerations 2. Potential Security (If Page O/P Source is viewed)
  •  Query String –  A String which is appended to the end of the page URL.  Can be used to send small amount of data and if security is not a concern  Can be used to pass small amount of data from 1 page to another. Advantages 1. No Server side resources used. 2. Simple implementation Disadvantages 1. Limited Capacity 2. Potential Security risk
  •  Cookies –  It is useful to store small amount of data on the Client side.  It can be temporary(with specific expiration time and date). Advantages 1. Configurable Expiration Rules 2. No Server Resources required 3. Simplicity Disadvantages 1. Size limitations 2. User-configured refusal 3. Less Secured
  • Server Side State Management Session State –  Stored in the Server’s memory and value can be accessed across page requests.  3 different modes of storing the Sessions.  InProc  State Server  SQL Server  Off  Advantages  Cookieless Support  Data Persistence  Disadvantages  Performance Consideration
  •  Application State  It is used to store global application specific information  Automatically created when a first request is made to a web application  Storing application state in the Server’s memory is better than storing the information in the database Advantages 1. Application Scope 2. Simple Implementation Disadvantages 1. Requires Server resources 2. Limited Durability of data (Server Crash or Shutdown)