ASP.NET State Service

One of the problems you learned about earlier involved session state management across a Web farm. In particular, when users come to a Web site that uses several servers that can serve a particular user at any time, the session state does not automatically carry over from machine to machine. Another problem with session state is that it typically runs in the same process space as the IIS service. As a result, if your IIS service goes down, you also lose all session states.

Using a Separate State Server Machine

If you wish to solve both of these problems, you need to move the session state management to an out-of-process component that is separate from the IIS service.

When the .NET Framework is installed, a new service called ...

Get ASP.NET Developer's JumpStart now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.