How to understand the application pool of IIS7
This article mainly explains "how to understand the application pool of IIS7". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to understand the application pool of IIS7".
In IIS 7, adding an application or a separate website automatically creates a corresponding "application pool" by default, which is also a major feature of IIS 7.
In the early days of IIS 5.0, when there was only one application pool, it was easy to "destroy the whole army and lose all the glory". Because all websites (or applications in virtual directories) "live" in a "pool", when the "pool" crashes, all sites are miserable.
Later in IIS 6, there was the concept of "application pool", but it is not automatically added by default, and the IIS administrator can add and configure it manually, so that the IIS has a strong isolation.
Application pools have the following advantages:
Improved server and application performance. For resource-intensive applications, you can assign them to their own application pools so as not to affect the performance of other applications.
Improved application availability. If applications in one application pool fail, applications in other application pools are not affected.
Improved security. By isolating applications, you can reduce the chances that one application will access other application resources.
In IIS 7, application pools operate in two modes: integrated mode and classic mode. The application pool mode affects how the server handles managed code requests. If the managed application runs in an application pool in integrated mode, the server uses the integrated request processing pipeline of IIS and ASP.NET to process the request. However, if the managed application runs in an application pool in classic mode, the server continues to route managed code requests through Aspnet_isapi.dll in the same way that the application runs in IIS 6.0.
Most managed applications should be able to run successfully in an application pool in integrated mode, but it is sometimes necessary to run in classic mode for version compatibility. Applications running in integrated mode should be tested first to determine if classic mode is really needed. When deploying asp.net mvc applications with IIS 7, you only need to select "integrate" instead of tedious configuration like in IIS 6 (setting up ISAPI mappings, adding wildcards.)
Thank you for reading, the above is the content of "how to understand the application pool of IIS7". After the study of this article, I believe you have a deeper understanding of how to understand the application pool of IIS7, and the specific usage needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
