【正文】 ute) class, the characteristics of its logo will be into a Web Services implementation. Many other processors will be installed in conjunction with . Of course, we can define your own processor. In all the HttpHandler in IIS is mapped to ISAPI and expansion, and these are in the HttpHandler in configuration for routing the request to a specific processor in the implementation of HTTP. Each processor is a. NET class to handle the specified extension. These processors can handle only a few simple lines of code to the Hello World, also similar to handle plex pages as well as the implementation of WebService. For now, just need to understand the expansion of the mapping is a basic mechanism, can use it to obtain a request in ISAPI, and then routing the request to a specific request to deal with the processor. ISAPI connection ISAPI is the underlying unmanaged Win32 API. It defines a single interface and is the optimal performance. To deal with the original use of the interface pointer (raw pointer), and a list of function pointer (function pointer tables) are used for callback. ISAPI provides the lowest stratum, highperformance interface, tool developers and vendors can use these interfaces to the IIS indepth. ISAPI is very low as a result, therefore, less suitable to use it to build applicationlevel procedures. ISAPI tend to be used as a bridge interface for highlevel tools to provide the function of the type of application services. For example, ASP and are as cold fusion (cold fusion) to build on top of the ISAPI. Most of Perl, PHP and JSP as the implementation of a number of thirdparty solutions, can be run in IIS. ISAPI is a very good tool for highlevel applications to provide a highperformance vertical access interface. This makes those highlevel application requires information from the ISAPI extract the information provided. In ASP and , the engine can be extracted ISAPI interface object, such as in the form: Request and Response, these objects can request information from the ISAPI read their content. As agreed, ISAPI support ISAPI extension of (extensions) and the ISAPI filter (filters). Request for expansion is to deal with interface with the Web Server to provide the input and outputrelated logic to deal with. In essence, it is a Service interface. ASP and are to achieve as ISAPI extension. ISAPI is the hook interface, it allows you to see into the IIS request and every request can be amended (including the input and output) or to change the module (such as: authentication, etc.) behavior. Incidentally, through two aspects: HTTP processor (corresponding ISAPI extension) and the HTTP module (ISAPI filter counterpart) is mapped to the ISAPI. 附錄 2：外文文獻中文譯文 體系結(jié)構(gòu) 是完全使用托管代碼處理 Web 請求的一個成熟引擎平臺。附錄 1：外文文獻原文 Architecture1 is fully managed code to deal with the use of Web request for a mature platform engine. It not only only WebForms and WebServices. processing engine is also a request, access to client requests it, and then through its builtin