aspnet體系結(jié)構(gòu)外文翻譯-文庫(kù)吧資料
2024-11-11 05:31本頁(yè)面
【正文】 the browser to the Let us start with a typical Web request lifecycle starting point. Users to type in the browser a URL, click on a hyperlink, to submit a HTML form (a post request), or a client program calls the WebService (through to provide services). The server side, IIS5 or IIS6 will receive the request. The bottom of and IIS through ISAPI extension of munication, and then through the , the request is usually with a route. Aspx page extensions. However, the process of how the work is entirely dependent on the HTTP processor (handler) implementation. The processor will be installed to handle the specified extension. In the IIS in,. Aspx by the extended application has been mapped to the ISAPI the dll file: . A trigger for each request, must be registered by a, and point to the extension to identify. Note: ISAPI is a custom Web request and deal with the first performance of IIS with the highest point of entry. Rely on the extension, routing a request to an appropriate processor, which is responsible for dealing with this request. For example, WebServices extension. Asmx not routing a request to a disk page, but will be routed to in the definition of the specified characteristics of the additional (WebMethodAttribute) 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 th
公司管理相關(guān)推薦
鄂ICP備17016276號(hào)-1