Controller

As explained in Django in Action

The MVC controller is the component responsible for handling interactions with application data and coordinating application behavior.

A controller is the input-and-control part of the MVC pattern: it connects user interactions with models and views. This matters when a site grows beyond static files and must handle data, comments, uploads, and application behavior. section 1.1.1

Django uses MVC as a useful mental model rather than a strict blueprint. Its view handles Python request-processing code, so the boundary between Django’s view and controller remains deliberately fuzzy. section 1.1.1 section 1.3

A typical request path looks like this:

• A web server passes the URL request to Django through WSGI. section 1.1.1
• Django checks urls.py and its urlpatterns list of path objects. section 1.1.1
• A path selects a Django view, implemented as a function or class that receives the request and returns a response document. section 1.1.1 section 1.3

Figure 1.4 Model—view—controller architectural pattern

Use the MVC diagram to distinguish the controller’s interaction role from the model’s data and business logic and the view’s presentation role. section 1.1.1

How Django in Action covers it

How deep it goes

Defines the controller and traces URL routing to views, while stopping short of prescribing a separate Django controller component.

Examples

Uses static-versus-dynamic websites, urls.py, urlpatterns, path objects, Django views, and request-response handling.

What you can do after

Understand how Django routes a browser request and where controller responsibilities appear within its view-centered architecture.

How it connects

Connects MVC with models, views, URL routing, templates, HTTP requests, and single-page applications.

liveBookmanning.com

Read Django in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  ASP.NET Core in Action, 3eA web API controller is an ASP.NET Core controller that handles HTTP API requests through action methods and produces machine-readable responses.
• 

  liveBookmanning.com
  Pro ASP.NET Core 7, Tenth EditionA controller is an ASP.NET Core MVC component that receives requests and coordinates processing to produce responses, including responses rendered from views.
• 

  liveBookmanning.com
  Unit Testing Principles, Practices, and PatternsA controller is a software component that coordinates work between other components without itself implementing substantial complex or business-critical logic.
• 

  liveBookmanning.com
  Spring in Action, Sixth EditionA controller class is a web-application component that receives and handles client requests.
• 

  liveBookmanning.com
  Building Web APIs with ASP.NET CoreAn ASP.NET Core controller is a component that handles web requests through action methods and framework-supported conventions.
• 

  liveBookmanning.com
  Web Components in ActionIn Model-View-Controller architecture, the coordination layer that handles input and mediates updates between the view and model.
• 

  liveBookmanning.com
  .NET in Action, Second EditionAn MVC controller is the component that receives requests or user input and coordinates the model and view used to produce a response.

Compare how 8 books explain controller →

Related concepts

• Model–view–controllerpart of · Model–view–controller is an architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.
• ControllerBasekind of · ControllerBase is the ASP.NET Core MVC base class providing controller behavior and action-result helpers without view-specific functionality.
• componentkind of · A software component is a modular part of a larger system that provides related functionality and interacts with other parts through defined boundaries or interfaces.
• RouteAttributeconfigured by · RouteAttribute is an ASP.NET Core attribute that associates a controller or action with a route template.
• routinguses · Routing is the selection of a path, destination, or processing component to direct an item, request, or flow toward an intended endpoint.

This explainer was generated by Manning's knowledge graph from the text of Django in Action. The section links point to the parts of the book it draws on.