ince the dawn of the Web, managing state in the stateless world of HTTP has been a problem for Web developers. More recently, various techniques for storing and retrieving data have emerged. In this article I will describe how ASP.NET developers can...
See more 
ince the dawn of the Web, managing state in the stateless world of HTTP has been a problem for Web developers. More recently, various techniques for storing and retrieving data have emerged. In this article I will describe how ASP.NET developers can maintain or pass state across page requests. In ASP.NET, there are several different ways to persist data between user requests—so many, in fact, that the novice developer is often confused about which object to use in a particular situation. In order to answer this question, there are three criteria that should be considered: * Who needs the data? * How long does the data need to be persisted? * How large is the set of data? By answering these questions, you can determine which object provides the best solution for persisting data between requests in an ASP.NET application. Figure 1 lists the different state management objects and describes when they should be used. In ASP.NET, four new objects have been added: Cache, Context, ViewState,... See less 
.value, '<a href="http://www.kaboodle.com/senfo/asp.net.html"><img alt="" src="http://cn1.kaboodle.com/hi/img/2/0/0/1c/f/AAAAAtp9pIQAAAAAABz9VA.png" width="65px" /></a>','http://www.kaboodle.com/senfo/asp.net.html','1');)
