1.8. Dispatcher View

Dispatcher View combines a controller and dispatcher with views and helpers to handle client requests and prepare a dynamic presentation as the response. Controllers do not delegate content retrieval to helpers, because these activities are deferred to the time of view processing. A dispatcher is responsible for view management and navigation and can be encapsulated either within a controller, a view, or a separate component. The Dispatcher View pattern handles the request and generates a response while managing limited business processing. 

UML representation


The following lists the benefits of using the Dispatcher View pattern:
  • Separates processing logic from view
  • Improves reusability

When to Use

You should use the Dispatcher View pattern when:
  • You have static views.
  • You have limited business processing.