Lære Front Controller Pattern

Definition

The front controller pattern is a design pattern where a single handler, typically a script like index.php, processes all incoming requests to an application, directing them to the appropriate part of the system for handling.

When you use the front controller pattern in your PHP application, every request no matter what page or resource is being accessed goes through a single entry point, usually called index.php. This script is placed at the root of your public directory, and it is responsible for initializing your application, loading the router, and dispatching the request to the correct controller and action. By funneling all requests through this one file, you gain complete control over how requests are handled and how responses are generated.

index.php

router.php


              12345678910
            
<?php
// index.php - Front Controller

require_once 'router.php';

// Get the current request URI
$requestUri = $_SERVER['REQUEST_URI'];

// Use the router to dispatch the request
dispatch($requestUri);

Centralizing request handling in this way brings several important benefits. First, it allows you to manage all routing logic in one place, making it much easier to update or extend. You can add authentication, logging, or error handling globally without repeating code across multiple files. This approach also helps you enforce consistent request processing, which is crucial as your application grows.

index.php

router.php


              12345678910111213
            
<?php
// index.php - Front Controller with Basic Error Handling

require_once 'router.php';

try {
    $requestUri = $_SERVER['REQUEST_URI'];
    dispatch($requestUri);
} catch (Exception $e) {
    // Handle errors gracefully
    http_response_code(500);
    echo "An internal error occurred: " . htmlspecialchars($e->getMessage());
}

By implementing the front controller pattern, you make your PHP application more secure and maintainable. Security improves because you can filter and validate all input in one place, reducing the risk of vulnerabilities. Maintenance is easier since changes to routing, error handling, or initialization only need to be made in the front controller, rather than in many separate files. This structure is especially helpful as your project becomes larger and more complex.

Alt var klart?

Takk for tilbakemeldingene dine!

Seksjon 2. Kapittel 3

Spør AI

Spør om hva du vil, eller prøv ett av de foreslåtte spørsmålene for å starte chatten vår

Sveip for å vise menyen

Definition

index.php

router.php


              12345678910
            
<?php
// index.php - Front Controller

require_once 'router.php';

// Get the current request URI
$requestUri = $_SERVER['REQUEST_URI'];

// Use the router to dispatch the request
dispatch($requestUri);

index.php

router.php


              12345678910111213
            
<?php
// index.php - Front Controller with Basic Error Handling

require_once 'router.php';

try {
    $requestUri = $_SERVER['REQUEST_URI'];
    dispatch($requestUri);
} catch (Exception $e) {
    // Handle errors gracefully
    http_response_code(500);
    echo "An internal error occurred: " . htmlspecialchars($e->getMessage());
}

Alt var klart?

Takk for tilbakemeldingene dine!

Seksjon 2. Kapittel 3