Introduction to ASP. NET ISAPI

ASP. NET is a very powerful platform for building Web applications. It provides great flexibility and capabilities that can be used to build all types of Web applications.

Most people are only familiar with high-level frameworks such as WebForms and WebServices-all of which are at the top of the ASP. NET hierarchy.

ASP. NET Request Processing in IIS 5

Description of the graph:

A notable feature of IIS 5.x is the separation of Web Server and real ASP. NET Application. As a Web Server, IIS runs on a process named InetInfo.exe. InetInfo.exe is a Native Executive, not a hosted program, but our real ASP. NET Application runs on a Worker Process called aspnet_wp. It loads CLR during initialization, so it is a managed environment.

ISAPI: an application that can process various extensions. ISAPI is short for the following words: Internet Server Application Programe Interface, Internet Server Application Interface.

Features of IIS 5 mode:

1. First, only one aspnet_wp process can be run on the same host at the same time, and each ASP. NET Application corresponds to an Application Domain, that is to say, each Application runs in the same Worker Process. Application Isolation is based on Application Domain rather than Process.

2. Second, ASP. net isapi is not only responsible for creating the aspnet_wp Worker Process, but also responsible for monitoring the Process. If the Performance of aspnet_wp is detected to a lower limit, ASP. net isapi is responsible for killing the process. When aspnet_wp is terminated, subsequent requests will cause ASP. net isapi to re-create a new aspnet_wp Worker Process.

3. Finally, since IIS and Application are running in their respective processes, the communication between them must adopt a specific communication mechanism. Essentially, the communication between the InetInfo Process of IIS and the Worker Process is the communication between different processes of the same machine (local interprocess communications), which is considered for Performance, they use Named pipe-based communication mechanisms. Communication between ASP. net isapi and Worker Process is implemented through a set of Pipe between them. ASP. net isapi uploads the Request to the Worker Process asynchronously and obtains the Response. However, the Worker Process is synchronized to ASP. net isapi to obtain some Server-based variables.

1. Analysis on PageBase and MasterPage of ASP. NET
2. XML Web Service Method of ASP. NET
3. Detailed description of ASP. NET environment deployment
4. Implement ASP. NET globalization
5. Solve the Problem of ASP. net ajax script errors