Understanding the ASP.NET MVC Execution Process

Posted chucklu

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Understanding the ASP.NET MVC Execution Process相关的知识,希望对你有一定的参考价值。

https://docs.microsoft.com/en-us/aspnet/mvc/overview/older-versions-1/overview/understanding-the-asp-net-mvc-execution-process

Requests to an ASP.NET MVC-based Web application first pass through the UrlRoutingModule object, which is an HTTP module.

This module parses the request and performs route selection.

The UrlRoutingModule object selects the first route object that matches the current request. (A route object is a class that implements RouteBase, and is typically an instance of the Route class.)

If no routes match, the UrlRoutingModule object does nothing and lets the request fall back to the regular ASP.NET or IIS request processing.

UrlRoutingModule选择第一个匹配的route object

 

From the selected Route object, the UrlRoutingModule object obtains the IRouteHandler object that is associated with the Route object.

Typically, in an MVC application, this will be an instance of MvcRouteHandler. The IRouteHandler instance creates an IHttpHandler object and passes it the IHttpContext object.

By default, the IHttpHandler instance for MVC is the MvcHandler object. The MvcHandler object then selects the controller that will ultimately handle the request.

UrlRoutingModule会从选择的route object中获取和route object相关的route handler,一般来讲是MvcRouteHandler

Route Handler会创建一个HttpHandler,并且传递HttpContext给HttpHandler,一般来讲是MvcHandler。MvcHandler负责选择Controller

 

Note

When an ASP.NET MVC Web application runs in IIS 7.0, no file name extension is required for MVC projects. However, in IIS 6.0, the handler requires that you map the .mvc file name extension to the ASP.NET ISAPI DLL.

 

The module and handler are the entry points to the ASP.NET MVC framework. They perform the following actions:

  • Select the appropriate controller in an MVC Web application.
  • Obtain a specific controller instance.
  • Call the controller‘s Execute method.

 

The following lists the stages of execution for an MVC Web project:

  • Receive first request for the application

    • In the Global.asax file, Route objects are added to the RouteTable object.
  • Perform routing

    • The UrlRoutingModule module uses the first matching Route object in the RouteTable collection to create the RouteData object, which it then uses to create a RequestContext (IHttpContext) object.
  • Create MVC request handler

    • The MvcRouteHandler object creates an instance of the MvcHandler class and passes it the RequestContext instance.
  • Create controller

    • The MvcHandler object uses the RequestContext instance to identify the IControllerFactory object (typically an instance of the DefaultControllerFactory class) to create the controller instance with.
  • Execute controller - The MvcHandler instance calls the controller s Execute method. |

  • Invoke action

    • Most controllers inherit from the Controller base class. For controllers that do so, the ControllerActionInvoker object that is associated with the controller determines which action method of the controller class to call, and then calls that method.
  • Execute result

    • A typical action method might receive user input, prepare the appropriate response data, and then execute the result by returning a result type. The built-in result types that can be executed include the following: ViewResult (which renders a view and is the most-often used result type), RedirectToRouteResult, RedirectResult, ContentResult, JsonResult, and EmptyResult.

 

以上是关于Understanding the ASP.NET MVC Execution Process的主要内容,如果未能解决你的问题,请参考以下文章

Understanding the JVM

Understanding the Module Pattern in JavaScript

Graying the black box: Understanding DQNs

mysql官方文档之Optimization(8.8 Understanding the Query Execution Plan)

每日一读Towards Understanding the Instability of Network Embedding

(转)Understanding Memory in Deep Learning Systems: The Neuroscience, Psychology and Technology Perspe