ASP.NET 2.0 State Management

When you've got only one web server, keeping track of users states is quite trivial. But if you've got a web farm to deal with, it suddenly becomes more detailed. Because of HTTP's stateless design, web browsers must make a new connection for every user request, disconnecting afterwards. Because of this, there is never a guarantee that a user will end up on the same web server, request after request. In the past, developers were faced with implementing custom solutions, which usually involved saving state information to a database server, which all web servers could then access. Fortunately, ASP.NET has simplified the process of maintaining state between multiple web servers in a web farm so that your clients never notice that they've moved from one server to the next. Here is a quick look at using Profile to aide you and your web projects in state management using some powerful features in .NET 2.0.