aspnet體系結構外文翻譯(編輯修改稿)
2024-12-09 05:31 本頁面
【文章內容簡介】 ut pared with the ASP, has been great progress. ISAPI is the underlying Win32style API, the interface it will have only 1 trillion, which is largescale development is very difficult. ISAPI is due to the underlying interface, so its speed is very fast. But for enterpriselevel development is very difficult to administer. Therefore, in a certain period of time, ISAPI mainly serve as a platform for other applications or the bridge interface. But in any case, ISAPI has not been abandoned. In fact, the Microsoft platform and the interface is through the IIS host. NET in the ISAPI extension to munication, and then runtime direct access to . ISAPI provides the core Web Server munication interface, and then use nonmanaged code request access to and issued in response to client requests. ISAPI provides the content object is similar to the public through the HttpRequest and HttpResponse, through a well designed, accessible interface, the way to managed objects exposed to nonhosted data. From 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 ISAP
公司管理相關推薦
鄂ICP備17016276號-1