Written by:
2009/04/06 09:12 AM 

We have so many thing to try and remember when learning a new language. Lots of things to try to understand. C# and the .NET framework is so large, that it can almost be too overwhelming. But then you also have to contend with the differences of windows programming and web programming.

One of the big differences is this idea of a disconnected application. In traditional windows programming, you can keep things in memory across your different applications functions. But with the web you get disconnected from the web server with in seconds. How can you, how do you track you applications state across a disconnected network?

In this lesson we will be looking at application state, and what .NET does to manage web application state for you. ASP.NET applications are hosted in a web server and are accessed over the stateless HTTP protocol. Attempting to manage state in Web applications goes against the fundamental design principles of the Web. 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.  As such, if the application uses stateful interaction, it has to implement state management on its own. ASP.NET provides various functionality for state management in ASP.NET applications.

Read more of this article @ Web Development with C# - Application State.

TrackbackPrint

Tags:

Categories:

Location: BlogsThe Brave Programmer