d.Page Controller

  1. Motivation
    1. To facilitate page navigation related implementation in MVC pattern.
  2. Summary
    1. This pattern is a way of implementing Controller of MVC application with mosty static navigation with moderate complexity.
    2. There is one-one mapping in between page and controller that may increase complexity for large projects
    3.  Page Controller Pattern 
       ASP.Net Implementation
       
       

  3. When to Use
    1. You decided to use the Model-View-Controller (MVC) 
    2. The application you are building constructs the Web pages dynamically, but the navigation between the pages is mostly static.
    3. Screen navigation logic is of moderate complexity.
  4. Related Patterns
    1. Intercepting Filter. This pattern is another construct to implement recurring functionality inside a Web application. The Web server framework can pass each request through a configurable chain of filters before passing it to the controller. Filters tend to deal with lower-level functions such as decoding, authentication, and session management, whereas Page Controller deals with application functionality. Filters also are not usually page-specific.
    2. Front Controller. This pattern is a more complex, but also more powerful alternative to Page Controller. Front Controller defines a single controller for all page requests, which enables it to make navigational decisions that span multiple pages.
    3. Model-View-Controller. Page Controller is an implementation variant of the controller portion of MVC.
  5. Related Technologies 
    1. ASP.Net : Provides mechanism to implement MVC and related patterns.
  6. References
    1. MSDN: Page Controller Tutorial
    2. MSDN: Implementing Page Controller in ASP.NET