The difference between IIS7 application Pool integrate mode and Classic mode

IIS7 also used for a long time, about application Pool integrate mode and Classic mode is what is mengmengdongdong, so determined to go to the official website to read the technical documents, finally dawned, special to share.

IIS introduced the Application Pool from 7, which solves the problem with IIS6 setup on the server (because it is set on the server, so you can't allow two application to run in two mode). The mode settings are also added, Integate mode and Classic mode, respectively. So what's the difference between these two patterns?

First of all, the IIS MODULE,IIS7 began to introduce the module, each module has its own function, module contains the IIS itself, called the native Module, and foreign introduced. and by. NET introduces a module called the managed module. If you look closely at the native module and the managed module, you will find that both are duplicated, especially the user authentication here, and how to invoke these modules is the main difference between the two patterns.

First talk about integrate Mode. In this mode, when a new request is received, the request transmits an ordered list of events, and IIS invokes the required native module and Managed module based on each event. Take the user authentication, if it is an ASP. IIS ignores the native module and goes directly to the managed module. This improves the efficiency of handling the request and ensures that all user authentication for the application is made. NET program management.

For Classic mode, it is the same as isolation mode in IIS6, a request comes in, IIS calls Native module processing first, and then calls aspnet_ if it needs to run managed code. Isapi.dll to parse, then call managed Module. If you use the form of authentication, then you have to go through the native module once authentication, and then call the managed code to run the Managed module certification, which is repeated two times. In addition, if a resource does not run managed code, then the authentication of managed code will not run, as in form, for example, if a static resource is invoked, only IIS native authentication will be invoked instead of form authentication. Classic mode is not as good as integrate mode in efficiency and deployment configurations.

To summarize, it is not difficult to see that if you write an ASP, running in integrate mode is the best option. Classic mode is more like a backward-compatible mode, and if your application has a problem with integrate mode, you can switch to that mode. In addition, another application scenario for Classic mode is the diversity of native modules, as well as the certifications that are native to the original. NET many more, if in order to reduce development costs, can also run under the Classic mode, of course, also bear the above-mentioned implementation efficiency and security issues.

IIS7 Application Pool Integrate the difference between mode and Classic mode