IIS5 and IIS6 the ASP. NET application life cycle and one of the page lifecycles.

Before writing this blog, know a lot of predecessors have written, their own swim, mainly to deepen their understanding of the details, on the other hand, I hope to browse this article readers a new understanding. Destined to be a long. There must be a new understanding, the illustrations are original.

I will list all the details that are involved in this article, and estimate the number of days of continuous updates.

When sending a request from the browser to the server, the entire process is grasped with the details. IIS5 and IIS6 are slightly different.

comprehensive understanding, grasp the details :

One, the request arrives at IIS again to the framework.

If you look at the following explanations, you need to know:

1, IIS5 and IIS6 all have inetinfo.exe processes.

2, Inetinfo.exe (Task Manager sees) the role of: including many services provided by IIS (HTTP, FTP, SMTP, etc.). Inetinfo.exe receives requests from the TCP/IP subsystem and transfers these requests to their respective services, which in turn interpret the request, execute the request, and return the results to the client. because all of these services run in the same process (Inetinfo.exe) , they can share cached data, such as file handles, account information, and log file data.

3, the name pipes named pipe is a protocol equivalent to the socket protocol in TCP/IP, which has a great resemblance to the respective advantages of LAN and WAN.

For more information, please refer to: http://msdn.microsoft.com/zh-cn/library/ms187892.aspx

4, the relationship between Inetinfo.exe and Aspnet_isapi.dll, where there is a "call" whether there is something wrong. That is, understanding the relationship between the. exe file and the. dll file, which is the point of reference.

5, registry: Here the primary role for the association of files. For details, please refer to the relevant information.

6, work process worker processes in IIS5 and IIS6 are called w3wp.exe and aspnet_wp.exe respectively. Both refer to the worker process, but the names are different.

7, communication between IIS and the framework: IIS is an unmanaged program, and the framework is a managed program, both passing the request through a resource bundle through the pointer ECB.

8, managed and unmanaged code code. Please refer to: http://www.cnblogs.com/Holmes-Jin/archive/2012/03/14/2396411.html

9, http. Sys in (C:\Windows\System32\drivers\), kernel mode and user mode, belonging to the operating system knowledge, this does not do in-depth study.

One,IIS5 accepts requests from the browser by inetinfo.exe and then calls "Aspnet_isapi.dll", Aspnet_isapi.dll " follow " named pipe protocol named Pipes" is transmitted through the ECB pointer and work Process (w3wp.exe), at which time aspnet_ Isapi.dll and w3wp.exe belong to different processes, and the transfer efficiency is not optimal, which is optimized in IIS6.

Second,IIS6 is the server's NIC driver kernel module C:\Windows\System32\drivers\http.sys listens to, then queries the registry Regitry This request is processed with the Application Association (one of the purposes of the Registry ) . To the w3svc service ( a service that is part of the Svchost.exe process, which can be seen in the Task Manager "service") ,and then view the inetinfo.exe delivery Aspnet_isapi.dll, at this time the aspnet_isapi.dll is drawn into the worker process (aspnet_wp.exe), addressed to the framework. Because aspnet_wp.exe and the framework belong to the same worker process, transmission efficiency is much better than IIS5. IIS6, it is completely optimized for ASP.

Yes, I also make a picture.

Second, the request arrives at the framework after the processing.

IIS5 and IIS6 the ASP. NET application life cycle and one of the page lifecycles.