PHP Design Patterns: Page Controller
The Page Controller design pattern is a common architectural approach used in web-based systems. It organizes the flow of control by dedicating a specific controller to handle the logic for an individual page or request. This approach helps isolate responsibilities, making the codebase easier to maintain and evolve.
What is the Page Controller?
In the Page Controller pattern, each page (or a group of pages with similar behavior) has its own controller, responsible for:
- Handling the request: Processing data sent from the client.
- Executing the page-specific logic: Validating input, interacting with models, or performing computations.
- Rendering a response: Passing processed data to a view (template) and returning the final response to the client.
Advantages of the Pattern
- Simple flow: Each page is mapped to its own dedicated controller.
- Separation of concerns: Each controller handles only its own logic.
- Maintainability: Changes to one page affect only its associated controller.
- Scalability: Adding new pages is straightforward and doesn’t disrupt existing functionality.
Basic Structure
A typical implementation involves the following components:
- Controllers: PHP files containing logic for specific pages.
- Routes: A routing mechanism to map URLs to controllers.
- Views: Templates used to render the user interface.
Flow
- The client sends a request to a specific URL.
- The routing system identifies the appropriate controller for the request.
- The controller executes the required logic and delegates the response rendering to a view.
- The view generates the final output and returns it to the client.
Implementation Example
File Structure
/htdocs /src /Controllers HomeController.php AboutController.php /Services ViewRenderer.php /Views home.html.php about.html.php /public index.php /routes.php composer.json
Autoloader
{ "autoload": { "psr-4": { "App\": "htdocs/" } } }
composer dump-autoload
Template
Template for the homepage and about.html.php.
<!DOCTYPE html> <html> <head> <title><?= htmlspecialchars($title) ?></title> </head> <body> <h1><?= htmlspecialchars($title) ?></h1> <p><?= htmlspecialchars($content) ?></p> </body> </html>
ViewRenderer
namespace App\Services; class ViewRenderer { public function render(string $view, array $data = []): void { extract($data); // Turns array keys into variables include __DIR__ . "/../../Views/{$view}.html.php"; } }
HomeController
Handles the homepage logic.
namespace App\Controllers; use App\Services\ViewRenderer; class HomeController { public function __construct(private ViewRenderer $viewRenderer) { } public function handleRequest(): void { $data = [ 'title' => 'Welcome to the Site', 'content' => 'Homepage content.', ]; $this->viewRenderer->render('home', $data); } }
AboutController
Handles the "About Us" page logic.
namespace App\Controllers; use App\Services\ViewRenderer; class AboutController { public function __construct(private ViewRenderer $viewRenderer) { } public function handleRequest(): void { $data = [ 'title' => 'About Us', 'content' => 'Information about the company.', ]; $this->viewRenderer->render('about', $data); } }
routes.php
Defines route mappings to controllers.
use App\Controllers\HomeController; use App\Controllers\AboutController; // Define the routes in an associative array return [ '/' => HomeController::class, '/about' => AboutController::class, ];
index.php
The application’s entry point.
/htdocs /src /Controllers HomeController.php AboutController.php /Services ViewRenderer.php /Views home.html.php about.html.php /public index.php /routes.php composer.json
Pros and Cons
Advantages
- Organization: Controllers are modular, each handling a specific page.
- Reusability: Views can be reused across different controllers.
- Debugging: Errors are easier to trace since each page has its own dedicated controller.
Disadvantages
- Increased number of controllers: Large projects can lead to a proliferation of controllers, requiring better organization.
- Code duplication: Common logic across controllers may be repeated. This can be mitigated by using a base controller class.
When to Use the Page Controller Pattern?
- Simple systems: Best for small to medium-sized web applications where each page has specific logic.
- Modular projects: When you want to isolate logic for easier maintenance.
- Without frameworks: Ideal for PHP projects without robust frameworks (like Laravel or Symfony).
For more complex projects, where there is significant logic reuse or multiple entry points, patterns like Front Controller or full MVC architecture may be more suitable.
The above is the detailed content of PHP Design Patterns: Page Controller. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...

Article discusses essential security features in frameworks to protect against vulnerabilities, including input validation, authentication, and regular updates.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.
