Learn the ASP. NET MVC framework secret Note-iis/asp. NET Pipeline (ii)

IIS7.0with theASP

iis7.0 Innovative improvements were made to the request's monitoring and distribution mechanism, mainly in the introduction of the window process Activation Service ( windows process activation service was ) shunt the original ( iis6.0 Span style= "Font-family:times New Roman" >w3svc Some of the features that are hosted. iis6.0 w3svc

1.HTTP Request receive: Receive HTTP. SYS to hear the HTTP request.

2. Configuration management: Configurethe related components by loading configuration information from the metabase (metabase).

3. Process Management: Create, recycle, and monitor worker processes.

IIS7.0The latter two sets of functions are implemented to wasin, but receiveHTTPthe requested task still falls on thew3svcthe head. wasthe introduction ofIIS7.0provides a non-HTTPprotocol support, which abstracts listeners for different protocols through the listener adapter interface. Specifically, except for monitoringHTTPof the requestHTTP. SYSOutside, wasUseTCPListeners , named pipe listeners, andMSMQlisteners are provided based onTCP, Named Pipes, andMSMQmonitoring support for the transport protocol.

corresponding to the 3 listeners, there are 3 monitoring adapters that provide an adaptation between the listener and the Listener adapter interface in was. These three types of non- HTTP listeners and listener adapters are defined in assembly SMSvcHost.exe . These three types of listener / listener adapters are designed for WCF .

Whether it's fromw3svcreceived byHTTPrequest, or throughWCFThe provided listener adapter receives requests for other transport protocols that are eventually passed to the was. If the corresponding worker process (for a single app process pool) has not yet been created, the wasCreate worker processes are created. wasload the relevant configuration information through the built-in configuration management module during request processing and configure the related components. IIS7.0Most of the configuration information is stored inXMLconfiguration file in the form, the basic configuration is stored in theapplicationhost.config.

1.3.4asp.net Integration

From the above introduction we found that iniis5.xand theIIS6.0in whichIISwith theASPis two separate pipes. Within their respective jurisdictions, they each have their own set of mechanisms forHTTPrequest for processing. Two pipes throughISAPIachieve "connectivity",IISis the first barrier, when theHTTPafter the necessary pre-processing is requested,IISthroughISAPIDistribute the request toASPpiping. WhenASPwithin the scope of its own piping, complete theHTTPwhen processing the request, the processed results are returned to theIIS,IISPost- processing after it is generatedHTTPreply responds to the request.

From another perspective,IIS is running in an unmanaged environment, while the ASP . NET pipeline is managed, so the ISAPI Or a link between an unmanaged environment and a managed environment.

Isolating the two pipelines brings at least some of the following limitations and deficiencies.

1. Repeated execution of the same operation.

2. The dynamic file is inconsistent with the static file processing.

3.IIS is difficult to expand.

For this purpose, the integration of the two is achieved in IIS7.0 and the following benefits can be obtained through integration.

1. Allow the IIS Moduleto be defined in both local code and managed code, which are registered with IIS iismodule To form a common request processing pipeline. This pipeline, composed of these iismodule, can handle all requests, regardless of the type of resource on which the request is based.

2. Apply some of the powerful features that ASP . NET provides to places that were previously difficult to reach.

3. Use the same approach to implement, configure, detect, and support some server features.

In the next chapter we explain the ASP.

Learn the ASP. NET MVC framework secret Note-iis/asp. NET Pipeline (ii)