ASP session functional defects
Currently, ASP developers are using session, but they have discovered the following defects in ASP session:
Process dependency: the ASP sessionstate is stored in the iisprogress, And the inetinfo.exeProgram. When the inetinfo.exe process crashes, the information is lost. In addition, restarting or disabling the IIS service will cause information loss.
Limitations of the range of session Status usage: when a user accesses another website from one website, the session information will not be migrated. For example, there may be more than one WWW server on the Sina website. After a user logs on, he/she will go to various channels, but each channel is on a different server, what if I want to share session information on these www servers?
Cookie dependency: in fact, the client's session information is stored in the cookie. If the client completely disables the cookie function, it cannot enjoy the function provided by the session.
In view of the above defects of ASP session, Microsoft designers are designing and developing ASP. net session, and the above defects are completely overcome, making ASP. net session has become a more powerful feature.
Three differences
Session exists on the server, while cookie exists on the client !!
The session does not require cookies to support and is not affected by browser settings. It records the information of each visitor and is independent on the server, which is safer than cookie!
The session exists in the memory, and the browser closes it and it is "dead". The cookie exists as a file, and the "survival" time can be modified.