ASP.NET 2.0 : A New Solution to an Old State Storage Problem

State management in Web applications is a contentious issue. Should you store user data per session or should you persist it across sessions? You can easily store information temporarily while someone navigates your site by using session state. That’s typically an in-memory data store indexed by a unique session key assigned to each new user and that lasts only for the duration of the "session" with the client. Storing information across sessions is typically done by building your own back-end data store indexed by some user identifier (typically obtained after a user logs onto the site).
More here

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s