asp論文外文翻譯---從底層了解aspnet的結(jié)構(gòu)-jsp程序(文件)
【正文】 st into the runtime. All the heavy lifting and processing, and even the request thread management happens inside of the engine and your code. As a protocol ISAPI supports both ISAPI extensions and ISAPI Filters. Extensions are a request handling interface and provide the logic to handle input and output with the Web Server – it’s essentially a transaction interface. ASP and are implemented as ISAPI extensions. ISAPI filters are hook interfaces that allow the ability to look at EVERY request that es into IIS and to modify the content or change the behavior of functionalities like Authentication. Incidentally maps ISAPIlike functionality via two concepts: Http Handlers (extensions) and Http Modules (filters). We’ll look at these later in more detail. 3 ISAPI is the initial code point that marks the beginning of an request. maps various extensions to its ISAPI extension which lives in the .NET Framework directory: 本文摘自 4 譯文 1 從底層了解 的結(jié)構(gòu) 摘要 Web程序的強(qiáng)大平臺(tái)，提供了強(qiáng)大的柔性和能力以至于它可以構(gòu)建任意的 Web程序。它不僅僅只是WebForms 和 WebServices。事實(shí)上， HTTP運(yùn)行時(shí)是一個(gè)組件，你可以把它宿主在IIS之外的應(yīng)用程序上。所以，此框架具有非常高的可擴(kuò)展性。除此之外，在容易開(kāi)發(fā)和性能之間， HTTP 運(yùn)行時(shí)還提供了最佳的靈活性。 使用 ，之前這些任務(wù)是使用 IIS上的 ISAPI擴(kuò)展和過(guò)濾來(lái)完成的。但對(duì)于企業(yè)級(jí)的程序開(kāi)發(fā)是相當(dāng)?shù)碾y于管理的。 ISAPI 提供了與 Web Server 通信的核心接口，然后 使用非托管代碼獲取請(qǐng)求以及對(duì)客戶(hù)端請(qǐng)求發(fā)出響應(yīng)。在服務(wù)器端， IIS5或者 IIS6將會(huì)收到這個(gè)請(qǐng)求。在 IIS中， .aspx經(jīng)由“應(yīng)用程序擴(kuò)展”被映射到 ISAPI 的 dll文件： 。舉個(gè)例子， WebServices的擴(kuò)展名 .asmx不會(huì)把一個(gè)請(qǐng)求路由到磁盤(pán)上的某一個(gè)頁(yè)面，而是會(huì)路由到在定義中附加了指定特性（ WebMethodAttribute）的類(lèi)，此特性會(huì)把它標(biāo)識(shí)成一個(gè) Web Services 的實(shí)現(xiàn)。每一個(gè)處理器都是一個(gè) .NET類(lèi)，用于處理指定的擴(kuò)展。2. RouteHandler Not really specific to MVC, the RouteHandler is the ponent that decide what to do after the route has been selected. Obviously if you change the RouteHandler you end up handling the request without MVC, but this can be useful if you want to handle a route directly with some specific HttpHanlders or even with a classic WebForm. 3. ControllerFactory The controller factory is the ponent that, based on the route, chooses which controller to instantiate and instantiate it. The default factory looks for anything that implements IController 7 and whose name ends with Controller, and than create an instance of it through reflection, using the parameterless constructor. But if you want to use Dependency Injection you cannot use it, and you have to use a IoC aware controller factory: there are already controller factory for most of the IoC containers. You can find them in MvcContrib or having a look at the Ninject Controller Factory. 4. ActionInvoker ActionInvoker is responsible for invoking the action based on it’s name. The default action invoker looks for the action based on the method name, the action name and possibly other selector attributes. Then it invokes the action method together with any filter defined and finally it executes the action result. If you read carefully you probably understood that most of the execution pipeline is inside the logic of the default ControllerActionInvoker class. So if you want to change any of these conventions, from the action method’s selection logic, to the way parameters are mapped to action parameters, to the way filters are chosen and executed, you have to extend that class and override the method you want to change. A good example of this, is the NinjectActionInvoker I developed to allow injection of dependencies inside filters. 5. ActionMethodSelectorAttribute Actions, with the default action invoker, are selected based on their name, but you can finer tune the selection of actions implementing your own Method Selector. The framework already es with the AcceptVerbs attribute that allows you to specify to w
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1