Building a PHP Framework: Part 8 – Routing
Part 7 got us up to speed on the container that will be used in the Analyze PHP Framework. In this post we’ll cover how routing works in general and specifically within PHP.
How Routing Works
Routing is the process of parsing a URI and determining the appropriate action to take.
For example, consider the following URI:
|
1 |
https://example.com/login |
How does a request like the one above result in a response to the user? Let’s break it down:
- The request is received by the application.1
- The application breaks down the request into its components. Things like: the method (ex: GET), host, path, etc.
- The application looks for a defined route that matches this request.
- Once found, it takes the defined action and returns a response.
A Laravel Example
For a real-world example, here’s one way the above example could be implemented in Laravel.
|
1 2 3 |
Route::get('/login', function() { return view('login'); }); |
We define a GET route for the /login URI. When that route is requested we return a response – in this case, HTML for the login page.
How Routers Work
There are a number of routers in the PHP ecosystem. They range from the more simplistic to feature-packed behemoths. Although they differ in size and complexity, they generally employ the same fundamental steps: parse the request, match the pattern, run some code, return a response.
The Symfony router (probably the most widely used PHP router) does this.
As does this one.
And this one.
A Very Simple PHP Router
To demonstrate these concepts let’s create a stupid simple, not at all useful, PHP router.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 |
<?php /** * First, let's define our Router object. */ class Router { /** * The request we're working with. * * @var string */ public $request; /** * The $routes array will contain our URI's and callbacks. * @var array */ public $routes = []; /** * For this example, the constructor will be responsible * for parsing the request. * * @param array $request */ public function __construct(array $request) { /** * This is a very (VERY) simple example of parsing * the request. We use the $_SERVER superglobal to * grab the URI. */ $this->request = basename($request['REQUEST_URI']); } /** * Add a route and callback to our $routes array. * * @param string $uri * @param Callable $fn */ public function addRoute(string $uri, \Closure $fn) : void { $this->routes[$uri] = $fn; } /** * Determine is the requested route exists in our * routes array. * * @param string $uri * @return boolean */ public function hasRoute(string $uri) : bool { return array_key_exists($uri, $this->routes); } /** * Run the router. * * @return mixed */ public function run() { if($this->hasRoute($this->request)) { $this->routes[$this->request]->call($this); } } } /** * Create a new router instance. */ $router = new Router($_SERVER); /** * Add a "hello" route that prints to the screen. */ $router->addRoute('hello', function() { echo 'Well, hello there!!'; }); /** * Run it! */ $router->run(); |
Run The Code
- Save this code locally as index.php.
- In your terminal navigate to the directory where you saved the script.
- Start the built-in PHP web server: php -S localhost:1234
- In your browser go to: http://localhost:1234/hello
Conclusion
I’ve touched on the very basics of routing, shared some routing examples from the PHP world, and built a extremely simple router. On a related note, I’ve started work on the router that will be used in the Analyze PHP framework. To keep up to speed on it, be sure to follow @AnalyzePHP on Twitter.
One last thing, be sure to checkout my newsletter! Each week I’ll send you a great email filled with updates, great links, tips & tricks, and other non-dev randomness. If you’re interested you can sign up using the form in the sidebar to the right 👉 or follow this link.
Footnotes
- There are a number of steps before the application receives a request. They’ve been left out for brevity. See: How Does The Internet Work?