IIS7 application pool

 

When you add an application or a separate website to IIS 7, a corresponding "application pool" is automatically created 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 cause "no loss, no loss ". Because all the websites (or applications under the virtual directory) are "resident" in a "pool", when this "pool" crashes, all the websites have a cup of cake.

Later in IIS 6, the concept of "application pool" was introduced, but it will not be automatically added by default. The IIS administrator can manually add and configure it. This way, IIS is highly isolated.

The application pool has the following advantages: www.2cto.com

Improved server and application performance. For applications that occupy a large amount of resources, you can allocate them to their own application pools to avoid affecting the performance of other applications.

 

Improved application availability. If an application in an application pool fails, applications in other application pools will not be affected.

 

Improved security. By isolating applications, you can reduce the chance that one application can access other application resources.

 

In IIS 7, the application pool has two running modes: integration mode and classic mode. The application pool mode affects how the server processes managed code requests. If a hosted application runs in an integrated application pool, the server uses the IIS and ASP. NET integrated request processing pipelines to process requests. However, if the hosted application runs in a classic-mode application pool, the server will continue to host code requests through the Aspnet_isapi.dll route, the method for processing requests is the same as that for applications running in IIS 6.0.

 

Most managed applications should be able to run successfully in an integrated application pool. To achieve version compatibility, they sometimes need to run in Classic mode. You should first test the applications running in integration mode to determine whether the Classic mode is required. When using IIS 7 to deploy the asp.net mvc application, you only need to select "integration". You do not need to configure it as complicated as in IIS 6 (set ISAPI ing and add wildcards ...)

The following is an explanation of the application pool "integration" and "classic" patterns on MDSN: (http://technet.microsoft.com/zh-cn/library/cc753449 (WS.10). aspx)

 

Author: dinglang_2009