Asp. NET Request Process-1

Client sends request to server

Enter the domain name->DNS resolution, specify the IP server (if the Web page directly enters the IP address directly to the server), and request arrives at server-HTTP. SYS accepts HTTP requests, forwards to ISAPI (which is a built-in service that is a component of the IIS server), and checks the suffix of the current request.   (The configuration of the suffix is inside the handler mapping service), according to the suffix (the ASP. NET MVC default pipe adds an ASD suffix to him) pipe communication to ASPNET_ISAPI (note that this is for sap.net and Php_isapi. JAVA_ISAPI, etc.), encapsulate the request of the website as httpworkrequest-> and then pass the httpworkerequest to httpruntime (httpruntime can be accessed in the program again, He is the gateway to the ASP. And then arrives at HttpApplicationFactory, a factory for the HTTP application he will create a HttpApplication (pipeline model is from him)

Keyword explanation

HttpRuntime and httpapplicatonfactory are light colors (from the network) because they are single-case. Describes that these two objects are created only once in the program.

Each time a request is made, a httpapplication is created, but HttpApplicationFactory internally maintains an object pool that is not destroyed immediately after the HttpApplication is created. will be placed in the pool.

Keyword explanation

Application pools: The concept in IIS is the memory space at the time the Web site runs.

Application domain:: In order to guarantee the key of the code the CLR wants to isolate the code between the different service functions, which can be achieved by creating multiple processes, but the creation of processes in the operating system is a time-consuming and resource-intensive thing, so the concept of AppDomain is introduced in the CLR. The AppDomain is primarily used to achieve isolation between the various AppDomain in the same process

Recommended https://www.cnblogs.com/asminfo/p/3999412.html

Httpruntime:ttpruntime is responsible for creating HttpContext objects and calling HttpApplicationFactory to create HttpApplication in the ASP. NET processing request.

Recommended https://www.cnblogs.com/kissdodog/archive/2013/05/07/3065208.html

HttpApplicationFactory: Create HttpApplication, manage HttpApplication pool.

HttpApplication: is a user request.

Recommended https://www.cnblogs.com/liangxiaofeng/p/5625976.html

Recommended https://www.cnblogs.com/cs_net/archive/2010/11/22/1883706.html

HttpContext: The user request and background processing information are placed in this type, which contains the user request process encountered events (can be specified by module and Global.asax, respectively)

Recommended article https://www.cnblogs.com/cs_net/archive/2010/11/22/1883706.html

Module: Registers the events in the HttpApplication. is an observer pattern (plus config file).

Handler: All requests go back to Handler (either the original WebForm or the current MVC.) Even a picture is a yes. ）。

Asp. NET Request Process-1