Import PHP files through the URL instead of the disk path

Question

When I use an architecture like MVC in a PHP project separating the models, controllers, services, views often using the functions include or require the application gets lost importing the PHP files located in other directories, and for that you need to pass the path of the full disk of the file location in order to prevent a PHP file inside the directory model to be imported is sought in /controllers/model where this problem often occurs when going back directories (../) for example.

I wonder if it is possible to import these files using the URL instead of the disk path because you do not need to keep entering or going back to each directory.

So it could matter simply by passing: /controllers/TerceiroController.class, for example, or localhost/projeto/controllers/TerceiroController.class rather than /var/www/html/...

Answer 1

Standardize with the use of autoloader in the PSR-4 standard: http://www.php-fig.org/psr/psr-4/

For example, the concept idea is to use namespace to facilitate route assembly.

The namespace feature is available from PHP 5.3.0.

Examples: http://www.php-fig.org/psr/psr-4/examples/

Answer 2

You cannot do this simply because PHP is a server-side scripting language.

You can use resources of a file in another URL, usually when it is passed by POST, this would be an API of some service, or even catch the return (output) of some page, for example.

However, it is not possible to do what you want, from the moment you use http:// (even if you omit and put only the external URL), you would no longer be on the "server side".

To solve your problem, declare a constant using define('RAIZ_PROJETO', dirname(__FILE__)) at index, as it will be global you can use to pick up the path, as require_once(RAIZ_PROJETO.'/models/seuModel.php')

Alert: Create global constants and use throughout your project can create a high coupling, ie, make your classes very dependent.

You can create a class to encapsulate this information and use dependency injection, as it is a MVC, it is likely that you will have to do this at some point in your project, whether with configuration files or something you need to have access to at various points but don’t want to create a direct dependency.

And it also doesn’t hurt to use a constant, you can, but there’s this downside.

The downside of creating a class and using DI would be the job of programming everything.