[ASP. NET] Session details

Preparations before reading this article Before reading this article, you need to understand the following knowledge. Otherwise, you may encounter different levels of problems in the reading process. Understand ASP/ASP. NET Programming Understand ASP/ASP. NET Session Models Understand ASP. NET Web Application Models Measure the test taker's knowledge about the functions, significance, and usage of the Web. config file for ASP. NET Web applications. Measure the test taker's understanding about how to use Internet Information Services (IIS ). Learn how to create a database in Microsoft SQL Server. Session model Overview What is Session? Simply put, it is the number that the server sends to the client. When a WWW server is running, several users may browse the website running on this server. When a user establishes a connection with the WWW server for the first time, the user establishes a Session with the server, and the server automatically assigns a SessionID to the user to identify the unique identity. This SessionID is a random string consisting of 24 characters on the WWW server. We will see it in the following experiment. This unique SessionID has great practical significance. When a user submits a form, the browser automatically attaches the user's SessionID to the HTTP header information (this is an automatic function of the browser and the user will not notice it ), after the server processes the form, it returns the result to the user corresponding to the SessionID. Imagine how the server knows which user submitted the form when two users register simultaneously without SessionID. Of course, SessionID has many other functions, which we will mention later. In addition to SessionID, each Session contains many other information. However, for ASP or ASP. NET Programming and programming, the most useful thing is to access ASP/ASP. NET's built-in Session object to store their own information for each user. For example, if we want to know how many pages a user visits our website browses, we may add the following to each page that a user may access: <% If Session ("PageViewed") = "" Then Session ("PageViewed") = 1 Else Session ("PageViewed") = Session ("PageViewed") + 1 End If %> You can use the following sentence to learn about several pages you have browsed: <% Response. Write ("You have viewed" & Session ("PageViewed") & "pages ") %> Some readers may ask: where does this seemingly array Session ("...") come from? Do I need to define it? In fact, this Session object is a built-in object of the WWW server with ASP interpretation capability. That is to say, this object has been defined for you in the ASP system, and you only need to use it. The variable name in Session ("...") is like the variable name. In Session ("...") = $, $ is the variable value. You only need to write a sentence to access the value in the variable .. on every page of the user. In fact, ASP has a total of seven built-in objects, including Session, Application, Cookie, Response, Request, Server, etc. Similar objects are also available in other server-side scripting languages such as JSP and PHP, but they are not the same in terms of naming or usage. 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.exe program is also used. 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. Introduction to the Web. config file Some ASP. NET programmers say: What is the Web. config file? I have never heard of it, but can the program I wrote work properly? Yes, you are right. Without the Web. config file program, it can run normally. However, if you create a large website, you need to make some overall configuration for the entire website, for example, you need to use the Web. config file. Although some options in the Web. config file can be configured through IIS, if the corresponding settings in Web. config also overwrite the configuration in IIS. In addition, the biggest convenience of the Web. config file is that you can access the settings in web. config by calling the System. Web namespace on the ASP. NET page. There are two types of Web. config: the server configuration file and the Web application configuration file, both named Web. config. This configuration file stores a series of information about the web pages written in which language, Application Security Authentication mode, and Session information storage mode on the current IIS server. This information is saved using XML syntax. If you want to edit it, use the text editor. The server configuration file takes effect for all applications on all sites on the IIS server. In. NET Framework 1.0, the Web. config file of the server exists in \ WinNT \ Microsoft. NET \ Framework \ v1.0.3705. The Web application configuration file Web. config is stored in various Web applications. For example, the root directory \ Inetpub \ wwwroot of the current website, and the current Web application is MyApplication, the root directory of the Web application should be \ Inetpub \ wwwroot \ MyApplication. If your website has only one Web application, the root directory of the application is \ Inetpub \ wwwroot. To add a Web application, add a virtual directory with the application starting point in IIS. The files and directories under this directory are considered as a Web application. However, adding a Web application through IIS does not generate a Web. config file for you. To create a Web application with a Web. config file, use Visual Studio. NET to create a Web application project. The Web. config configuration file of the Web application is optional and optional. If not, each Web application uses the Web. config configuration file of the server. If yes, the corresponding values in the Web. config configuration file of the server will be overwritten. In ASP. NET, modifications to Web. config will automatically take effect immediately after they are saved. You do not need to restart the Web application to take effect after modifying the configuration file in ASP. Session configuration information in the Web. config file After opening the configuration file Web. config of an application, we will find the following section: <SessionState Mode = "InProc" StateConnectionString = "tcpip = 127.0.0.1: 42424" SqlConnectionString = "data source = 127.0.0.1; Trusted_Connection = yes" Cookieless = "false" Timeout = "20" /> This section describes how the application stores Session information. The following operations mainly aim at this configuration section. Let's take a look at the meaning of the content contained in this section. The syntax of the sessionState node is as follows: <SessionState mode = "Off | InProc | StateServer | SQLServer" Cookieless = "true | false" Timeout = "number of minutes" StateConnectionString = "tcpip = server: port" SqlConnectionString = "SQL connection string" StateNetworkTimeout = "number of seconds" />   The required attribute is Attribute Option Description Mode Set where to store Session information Off Set to not use the Session Function InProc Set the Session to be stored in the process, that is, the ASP storage method. This is the default value. StateServer Set to store sessions in independent State services. SQLServer Set to store sessions in SQL Server. Optional attributes: Attribute Option Description Cookieless Set where the Session information of the client is stored Ture Cookieless Mode False Use Cookie mode. This is the default value. Timeout Sets the number of minutes after which the server automatically abandons the Session information. The default value is 20 minutes. StateConnectionString Set the server name and port number used to store Session information in the status service, for example, "tcpip = 127.0.0.1: 42424 ". WhenModeThe value isStateServerYes, this attribute is required. SqlConnectionString Set the connection string when connecting to SQL Server. For example, "data source = localhost; Integrated Security = SSPI; Initial Catalog = northwind ". WhenModeThe value isSQLServerThis attribute is required. StateNetworkTimeout Sets the number of seconds after the Session state is stored in StateServer mode and the TCP/IP connection between the Web server and the server that stores the status information. The default value is 10 seconds. Storage of client Session Status in ASP. NET In our previous Session model introduction, we can find that the Session status should be stored in two places: client and server. The client is only responsible for saving the SessionID of the corresponding website, while other Session information is stored on the server. In ASP, the SessionID of the client is actually stored as a Cookie. If the user chooses to disable cookies in the browser settings, then he will not be able to enjoy the convenience of the Session, or even access some websites. To solve the above problems, the Session information storage methods of the client in ASP. NET are divided into Cookie and Cookieless. In ASP. NET, by default, Session information is stored on the client using cookies. If you want to use Cookieless on the client to store Session information, the method is as follows: Find the root directory of the current Web application, open the Web. Config file, and find the following section: <SessionState Mode = "InProc" StateConnectionString = "tcpip = 127.0.0.1: 42424" SqlConnectionString = "data source = 127.0.0.1; Trusted_Connection = yes" Cookieless = "false" Timeout = "20" /> In this section, cookieless = "false" is changed to cookieless = "true". In this way, the Session information of the client is no longer stored using cookies, but stored through URLs. Close the current IE, open a new IE, and re-access the Web application, you will see something similar to the following: Http: // localhost/MyTestApplication/(ulqsek45heu3ic2a5zgdl245)/default. aspx indicates the Session ID of the client. Note that this information is automatically added by IIS and does not affect the normal connection. Storage of server Session Status in ASP. NET Preparations To better experience the experiment, you can create a page named SessionState. aspx and add the following code to <body> </body>. <Scriptrunat = "server"> Sub Session_Add (sender As Object, e As EventArgs) Session ("MySession") = text1.Value Span1.InnerHtml = "Session data updated! <P> Your session contains: <font color = red> "&\ Session ("MySession"). ToString () & "</font>" End Sub Sub CheckSession (sender As Object, eAs EventArgs) If (Session ("MySession") Is Nothing) Then Span1.InnerHtml = "NOTHING, session data lost! " Else Span1.InnerHtml = "Your session contains: <font color = red> "&\ Session ("MySession"). ToString () & "</font>" End If End Sub </Script> <Formrunat = "server" id = "Form2"> <Inputid = "text1" type = "text" runat = "server" name = "text1"> <Inputtype = "submit" runat = "server" OnServerClick = "Session_Add" Value = "Add to Session State" id = "Submit1" name = "Submit1"> <Inputtype = "submit" runat = "server" OnServerClick = "CheckSession" Value = "View Session State" id = "Submit2" name = "Submit2"> </Form> <Hrsize = "1"> <Fontsize = "6"> <spanid = "span1" runat = "server"/> </font> This SessionState. aspx page can be used to test whether Session information is lost on the current server. Store Server Session information in the process Let's go back to the section in the Web. config file: <SessionState Mode = "InProc" StateConnectionString = "tcpip = 127.0.0.1: 42424" SqlConnectionString = "data source = 127.0.0.1; Trusted_Connection = yes" Cookieless = "false" Timeout = "20" /> When the mode value is InProc, it indicates that the server is using this mode. This method is the same as the previous ASP mode, that is, the server stores Session information in the IIS process. When IIS is disabled or restarted, the information is lost. However, this mode also has its own biggest advantage, that is, the highest performance. It should be that all Session information is stored in the IIS process, so IIS can quickly access this information, the performance of this mode is much faster than that of Session information stored outside the process or stored in SQL Server. This mode is also the default mode for ASP. NET. Now let's do a test. Open the SessionState. aspx page and enter some characters to store them in the Session. Then, let's restart IIS. Note that it is not to stop the current site and start again, but to right-click the node of the machine name in IIS and choose restart IIS. (To restart IIS when NT4 is used, you must restart the computer. Microsoft returns SessionState. on the aspx page, check the Session information and find that the information has been lost. Store Server Session information outside the process First, let's open the management tool> Service, find the Service named ASP. NET State Service, and start it. In fact, this service is to start a process to save Session information. After starting this service, you can see a process named aspnet_state.exe in the Windows Task Manager> process. This is the process for saving Session information. Return to the preceding section in the Web. config file and change the mode Value to StateServer. Open another IE after saving the file, open the SessionState. aspx page, and save some information to the Session. At this time, let's restart IIS and return to the SessionState. aspx page to view the Session information. In fact, this method of storing Session information outside the process not only means that the information can be stored in the local process, but also the Session information can be stored in other server processes. In this case, you not only need to change the mode Value to StateServer, but also need to configure the corresponding parameters in stateConnectionString. For example, if you want to store the Session in the process of a computer whose IP address is 192.168.0.2, you need to set it to stateConnectionString = "tcpip = 192.168.0.2: 42424 ". Of course, do not forget to install. NET Framework on the computer 192.168.0.2 and start the ASP. NET State Services Service. Store Server Session information in SQL Server First, let's make some preparations. Start the SQL Server and SQL Server proxy services. Execute a script file named InstallSqlState. SQL in SQL Server. This script file will create a database in SQL Server for storing Session information and an SQL Server proxy job for maintaining the Session information database. You can find the file in the following path: [System drive] \ winnt \ Microsoft. NET \ Framework \ [version] \ Then open the query analyzer, connect to the SQL Server, open the file and execute it. Wait a moment and the database and job will be created. In this case, you can open the Enterprise Manager and see a new database called ASPState. However, this database only contains some stored procedures and does not use user tables. In fact, Session information is stored in the ASPStateTempSessions table of the tempdb database, and the other ASPStateTempApplications table stores the Application Object Information in ASP. These two tables are also created by the script just now. In addition, you can view "manage"> "SQL Server proxy"> "job" and find another job called ASPState_Job_DeleteExpiredSessions. This job actually deletes expired Session information from the ASPStateTempSessions table every minute. Then, we return to the Web. config file and change the mode Value to SQLServer. Note: You must also modify the sqlConnectionString value in the following format: SqlConnectionString = "data source = localhost; Integrated Security = SSPI ;" Data source refers to the IP address of the SQL Server. If SQL Server and IIS are a Server, write 127.0.0.1. Integrated Security = SSPI means to use Windows Integrated Identity Authentication, so that accessing the database will use ASP.. NET identity, through this configuration, you can obtain better security than the SQL Server authentication method using userid = sa; password = password. Of course, if SQL Server runs on another computer, you may need to maintain consistency between the two sides through Active Directory domains. Similarly, let's do a test. Add the Session information to SessionState. aspx and you will find that the Session information already exists in SQL Server. Even if you restart the computer, the Session information will not be lost. Now you have fully seen what the Session information looks like and is stored in SQL Server. What you can do depends on your performance. Haha. Summary Through this article, you can see that in terms of Session management and maintenance, ASP. NET has made great progress over ASP. We can select a suitable method at will. For enterprise applications, this is undoubtedly beneficial to server synchronization, server stability, and reliability. I believe that with the support of powerful Microsoft, the new generation of e-commerce platforms will be built better! At the same time, you will also find that the entire technology includes the integration of operating systems, Web Services, and database technologies. I believe that Windows is not Unix stable, IIS is not Apache stable, and SQL Server is not powerful as Oracle. But who can perfectly link them together? So, although Microsoft is not too strong in every aspect, if Microsoft's things are integrated together, who would say that it is not powerful? Microsoft is Microsoft!

Source: Flying Technology Network