Structuring the PHP Router class with MVC

Question

A friendly url of the type:

www.meusite.com.br/controlador/metodo/argumentos

Is treated in my class Request, where I "explode" the url, separating it into segments, which are respectively, $controller, $action and $args, who will be returned to my class Route, where the application’s "routing" is done. So far Ok.

Problem

The problem is that you simply add a subdirectory. (So I get all worked up, because I’m a beginner in PHP applications with MVC, mainly in the concepts of classes Route and Request).

Directory structure

What is "picking up" is that, as I described the process in the first paragraph, the application will work perfectly without the subdirectories Usr and Adm, having only the following hierarchy.

For the whole process is in accordance with the Router and the Request.

Class Router

class Router
{
    public static function run(Request $request)
    {
        $controller= $request->getController();
        $action= $request->getAction();
        $args = (array) $request->getArgs();
        $controller = 'Application\Controller\\' . ucfirst($controller);
        $controller = new $controller();
        if (!is_callable(array($controller, $action))) {
            // Algum comando.
        }
        call_user_func_array(array($controller, $action), $args);
    }
    // Mais métodos

}

The above code is responsible for the inclusion of Controllers and the call to methods based on what was returned by Request. (this one doesn’t have much code, so I’ll just put the section that deals with the url)

Request

public function __construct()
{
    if (!isset($_GET["url"])) return false;

    $segments = explode("/", $_GET["url"]);
    $this->controller = ($controller = array_shift($segments)) ? $controller : "index";
    $this->action = ($action = array_shift($segments)) ? $action : "main";
    $this->args = (is_array($segments[0])) ? $segments : array();
}

Question

I would like to know what changes I should make to both codes so that a call to a controller, in any of the subdirectories, can be made successfully through the following format: url

www.meusite.com.br/nome_do_subdiretorio/controlador/metodo/argumentos

I apologize for the size of the question, but I tried to make it complete rsrs

Update

Controller Index

Exemplifying with this controller, it would be the standard, case a url came as follows: www.meusite.com.br/nome_do_subdominio/

namespace Application\Adm\Controller;

use MamutePost\Controller;

class Index extends Controller
{
    // ... Métodos
}

Mamutepost is a folder inside Vendor where I put my "mini-framework", which I developed to work with MVC.

Answer 1

Well initially I would change your class Request because just as it’s programmed, it makes the route identification mechanism very static for just that situation. Note how the simple class below makes it possible to identify generic routes according to a regular expression.

class Router {

  private static $routes = array();

  private function __construct() {}
  private function __clone() {}

  public static function route($pattern, $callback) {
    $pattern = '/^' . str_replace('/', '\/', $pattern) . '$/';
    self::$routes[$pattern] = $callback;
  }

  public static function execute($url) {
    foreach (self::$routes as $pattern => $callback) {
      if (preg_match($pattern, $url, $params)) {
        array_shift($params);
        return call_user_func_array($callback, array_values($params));
      }
    }
  }
}

this way you record the routes of your application and use the callback function to make the call to the due controller:

//registro da rota http://www.meusite.com.br/index/main
Router::route('http://www.meusite.com.br/index/main', function(){
  print "Application\Index\Main" . "<br/>";
});

//registro da rota http://www.meusite.com.br/nome_do_subdiretorio/controlador/metodo/argumentos
Router::route('http://www.meusite.com.br/(\w+)/(\w+)/(\w+)/(\w+)', function($folder, $controller, $action, $args){
  print "Application\\" . $folder . "\\" . $controller . "<br/>";
});

thus requester would be in charge of only calling the route class by passing the url in question:

Router::execute("http://www.meusite.com.br/index/main");
Router::execute("http://www.meusite.com.br/nome_do_subdiretorio/controlador/metodo/argumentos");

a clean, simple and efficient approach to a basic route system credits: http://upshots.org/php/php-seriously-simple-router