aspnet體系結(jié)構(gòu)外文翻譯-預(yù)覽頁
【正文】 channels, the request to an end, in the end, developers can add logic to deal with this request code. In fact the engine and HTTP or Web Server is pletely separate. In fact, HTTP is a runtime ponents, you can host it in IIS on the outside of the application, and even can be, and other services together. Pipeline through the use of builtin routing the request, HTTP runtime to provide a set of plex, but very elegant mechanism. In dealing with every aspect of the request are a lot of objects, but the majority of objects or events can be derived from the expansion interface. Therefore, this framework has a very high scalability. A mechanism through which to enter a lower level interface, such as: caching, authentication, authorization, such as is possible. You can process the request before or after the content filtering, or simply to match the signature of the designated client requests directly to your router or to other code in the URL. For the same thing can be dealt with through different methods, and the realization of the code are very intuitive. In addition, between the easy development and performance, HTTP operation was to provide the best flexibility. is designed with administration and manageability in mind. We recognize that while simplifying the development experience is important, deployment and maintenance in a production environment is also a key ponent of an application39。s fastest web server, Inter Information Services. also introduces key performance benefits over previous versions. Construction of the entire engine entirely in managed code, all functions are an extension of the expansion through the provision of managed code. For the powerful. NET framework, to use their own things, to build a mature, highperformance engine architecture has bee a probate. Nevertheless, it is important that, is the most impressive forwardlooking design, which in its work on very easily, and provides a hook almost any part of the request to deal with these capabilities. can be used to plete some tasks, these tasks prior to the use of IIS39。實(shí)際上這個(gè)引擎和 HTTP 或者 Web Server 是完全分開的。所以，此框架具有非常高的可擴(kuò)展性。除此之外，在容易開發(fā)和性能之間， HTTP運(yùn)行時(shí)還提供了最佳的靈活性。 配置的空氣污染指數(shù)。 前匯編工具。 健康監(jiān)測(cè)和追蹤。 靈活的可擴(kuò)展性 是一個(gè)良好的因素和公開的制度，任何組件可以很容易地取代自訂的執(zhí)行情況。 包括改進(jìn)的支持，控制可擴(kuò)展性，如更多的基地班概括的共同行為，提高設(shè)計(jì)師的支持，更多的空氣污染指數(shù)為互動(dòng)與客戶端腳本，元數(shù)據(jù)驅(qū)動(dòng)的支持，新功能，如主題和無障礙的核查，更好的國家管理，以 及更多。此外， sqldatasource 控制，船舶在方塊中已內(nèi)置支持，任何 托管提供實(shí)現(xiàn)新的供應(yīng)商工廠模型在 。為 xsd 文件類型化的 DataSet 對(duì)象。 包括表達(dá)的建設(shè)者為參照字符串資源的本地化，連接字符串，應(yīng)用程序設(shè)置和個(gè)人的價(jià)值觀。 整個(gè) 引擎完全構(gòu)建在托管代碼里，所有的擴(kuò)展性功能都是通過托管代碼的擴(kuò)展提供。盡管還有一些限制，但與 ASP 相比，已經(jīng)有了很大的進(jìn)步。所以，在一定的時(shí)間內(nèi)， ISAPI 主要充當(dāng)其它應(yīng)用程序或平臺(tái)的橋接口。 ISAPI 提供的內(nèi)容經(jīng)由公共對(duì)象類似于 HttpRequest 和 HttpResponse，通過一個(gè)設(shè)計(jì)優(yōu)良的、可訪問的接口，以托管對(duì)象的方式暴露非托管數(shù)據(jù)。 的底層通過 ISAPI 擴(kuò)展與 IIS 通信，然后，通過 ，這個(gè)請(qǐng)求通常被路由到一個(gè)帶有 .aspx 擴(kuò)展名的頁面。每一個(gè)觸發(fā) 的請(qǐng)求，都必須經(jīng)由一個(gè)已經(jīng)注冊(cè)的，并且指向 的擴(kuò)展名來標(biāo)識(shí)。許多其它的處理器將隨著 一起被安裝。而這些處理器可以處理簡(jiǎn)單到只有幾行代碼的 Hello World，也可以處理復(fù)雜到類似 的頁面以及執(zhí)行 WebService。用這些接口處理原始指針（ raw pointer），而函數(shù)指針列表（ function pointer tables）則用于回調(diào)。例如， ASP 和 都是被當(dāng)作冷聚變（ cold fusion）構(gòu)建于 ISAPI之上。在 ASP 和 里，引擎可以提煉 ISAPI 接口提供的表單里的對(duì)象如： Request 和 Response，這些對(duì)象可以從 ISAPI 請(qǐng)求的信息中讀取它們各自的內(nèi)容。 ASP和 ISAPI擴(kuò)展的實(shí)
公司管理相關(guān)推薦
鄂ICP備17016276號(hào)-1