NET of session and distributed session solution

Recently has been in the tangled net implementation of distributed sessions, now will be the recent personal feelings recorded as follows, if there is any better solution please advise.

1. What is session:

The Session object stores the properties and configuration information required for a specific user session. This way, when a user jumps between the application's Web pages, the variables stored in the session object are not lost, but persist throughout the user's session. When a user requests a Web page from an application, if the user does not yet have a session, the Web server automatically creates a Session object. When the session expires or is discarded, the server terminates the session. One of the most common uses of Session objects is to store the user's preferences. (Degree Niang)

Personal Summary: Because the HTTP protocol is stateless, and we want to know some of the user's last access when building a Web site, this requires a mechanism to hold the information that the user accesses. Since you want to save the information, then you must consider the storage of data, where is the storage of data exist? BS architecture of the system, only involved in a client and server, now is the case, the session data is so implemented, there are stored in the client, there are stored on the server, there are two combinations of use, then the question is how the data is stored? What data the client needs to store, and if it throws away the business data from the client, the rest should be stored by the server .... (It takes time to write a blog, a day to write a little)

Implementation of Session in 2.net

3. Custom distributed session implementation, support for high-scale, cross-platform

4. The Ultimate Solution

NET of session and distributed session solution