{"id":59859,"date":"2018-05-03T15:20:26","date_gmt":"2018-05-03T09:50:26","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=59859"},"modified":"2024-04-12T14:20:49","modified_gmt":"2024-04-12T08:50:49","slug":"angular-form-state-management","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/angular-form-state-management\/","title":{"rendered":"Angular Form State Management"},"content":{"rendered":"

Angular Form State Management<\/h1>\n

State management is the process by which you maintain state and page information over multiple requests for the same or different pages.<\/p>\n

As is true for any HTTP-based technology, Web Forms pages are stateless, which means that they do not automatically indicate whether the requests in a sequence are all from the same client or even whether a single browser instance is still actively viewing a page or site. Furthermore, pages are destroyed and recreated with each round trip to the server; therefore page information will not exist beyond the life cycle of a single page.<\/p>\n

ASP.NET provides multiple ways to maintain state between server round trips. Choosing among the options for state management available in ASP.NET will depend heavily upon your application, and it should be based on the following criteria:<\/p>\n

How much information do you need to store?
\nDoes the client accept persistent or in-memory cookies?
\nDo you want to store the information on the client or server?
\nIs the information sensitive?
\nWhat sorts of performance criteria do you have for your application?<\/p>\n

ASP.NET supports various client-side and server-side options for state management.<\/p>\n

Client-side options are:<\/p>\n

The View State property
\nHidden fields
\nCookies
\nQuery strings<\/p>\n

Server-side options are:<\/p>\n

Application state
\nSession state
\nDatabase<\/p>\n

A new instance of the Web page class is created each time the page is posted to the server. In traditional Web programming, this would typically mean that all information associated with the page and the controls on the page would be lost with each round trip. For example, if a user enters information into a text box, that information would be lost in the round trip from the browser or client device to the server.<\/p>\n

To overcome this inherent limitation of traditional Web programming, ASP.NET includes several options that help you preserve data on both a per-page basis and an application-wide basis. These features are as follows:<\/p>\n

View state<\/p>\n

Control state<\/p>\n

Hidden fields<\/p>\n

Cookies<\/p>\n

Query strings<\/p>\n

Application state<\/p>\n

Session state<\/p>\n

Profile Properties<\/p>\n

View state, control state, hidden fields, cookies, and query strings all involve storing data on the client in various ways. However, application state, session state, and profile properties all store data in memory on the server. Each option has distinct advantages and disadvantages, depending on the scenario.<\/p>\n

IT Professionals, Web Developers, web programmers, IT students can Apply for the certification course and get ahead.<\/strong><\/p>\n

\"\"<\/a><\/p>\n