Personal Insights on MVC in PHP_PHP Tutorial

After nearly a month of research on MVC, I also have my own MVC process and framework through the guidance of friends online. However, I feel that there are still many limitations and flexibility, but I don’t know how. For such specific improvements, I will publish my process and thoughts today, hoping that someone with expertise can give me some advice.
1. Entrance
The entry file can be a single file or multiple files. The one I use now is basically multiple files, but the contents of the entry files are basically the same. This will serve as a basis for future modifications to other entry methods,
1 2 require 'command/config.php';
3 require 'command/app.php';
4 app::run($config);
5 ?>
First of all, it goes without saying that everyone can see that the system configuration file is loaded, and then the system configuration is loaded through the engine.
2. Engine

1 public function run($config){
2 header("Content-type:text/html;charset=utf-8");
3 SELF :: $ config = $ config; // Load the system configuration
4         self::copyright();
5         self::testsystem();                                                                                                                                                                                                                                                                     . 6         self::setsystem();                                                                                                                                                                                              7         self::incinfo();
8          if(!IN_WEB){exit('The website is closed for maintenance, please visit later!');}
9        defined('KEHENG_DEBUG') or define('KEHENG_DEBUG',true); // Whether to debug mode
10 
11           self::setpath();                                                                                                                                                                                                                                                                    12 self::getdatabase(); //Test database
13 self::loadlib(); //Load library
14 self::getRouteConfig(); //Run the route and load the controller
15 }

In the engine, the configuration file is first set, then the system parameters are tested, the system module is loaded, the website information file configured is obtained, the path required by the website is set, the database parameters in the system configuration are tested, the library file is loaded, and finally the route is loaded to obtain the request address. I don’t know if this process is correct, it’s just a set I wrote based on my own learning, but it lacks cache. What should be the specific cache settings?
The database test here is based on which type of database is configured, and then the encapsulation file for the operation of this type of database is loaded.
3. Routing
The following is the last function above, which loads the controller file and obtains the request method according to the configuration file.

1 public function getRouteConfig(){
2        $route_type=self::$config[route][url_type];
3       switch($route_type){
4         case 1:
5                        //echo $_SERVER['SCRIPT_NAME'].'
';
6               $query_string=$_SERVER['QUERY_STRING'];
7                          //echo $_SERVER['REQUEST_URI'].'
';
8                  $urlstr=$_GET['controller'];
9            break;
10 case 4:
11                 $url = end(explode('/', $_SERVER["PHP_SELF"]));
12                   $urlstr = strtolower(substr($url,0,-4));
13 break;
14
15 }
16 if(file_exists(Contr_DIR.'Controller.php')){
17              require Contr_DIR.'Controller.php';
18                  //echo $urlstr;
19              $template = self::$config['Templates'];
20           controller::load($urlstr,$template);
21 }else{
22 exit('Controller file does not exist');
23 }
24
25 }

4. Controller
The controller file is also quite simple. It just loads the model file and view file based on the address analyzed by the route,

1 class controller{
2 public $obj;
3 public function load($url,$template){
4 
5         $config=$template;
6         if(file_exists(Model_DIR.$url.'.model.php')){
7               $views = new views;
8                 //echo Model_DIR.$url.'.model.php';
9             require Model_DIR.$url.'.model.php';
10             $temp = $config[$url][0];
11                 if($temp!='' && $temp!=null && isset($temp)){
12 if(file_exists(Templ_DIR.$temp)){
13                            //echo Templ_DIR.$temp;
14                                                     require Templ_DIR.$temp;
15           }else{
16 exit('View file does not exist!'.$temp);
17 }
18            }else{
19 exit('This page has no display template set!'.$temp);
20 }
21             unset($views);
22 }else{
23 exit('The model file does not exist:'.$url.'.model.php');
24 }
25 }
26}

But one thing to note is that all the data that needs to be output in the model file is output through a class such as views, including all system parameters in the view file in the package. I don’t know if this method is unnecessary. It turns out that the purpose is to encapsulate all the data to be output.

Other template files are also encapsulated with classes. Experts should know how to write them specifically. These are just my personal opinions, but how to write cache is still a vague concept. Is it reading data? When , the direction should be to read the cache, then determine whether the cache exists, and then determine whether the cache needs to be established? The specific operation method is still not very clear. I hope someone can give me some advice.

Excerpted from Jiuhu Technology

http://www.bkjia.com/PHPjc/478233.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/478233.htmlTechArticleAfter nearly a month of research on MVC, I also have my own set of methods through the guidance of friends online. MVC process and framework, but I feel that there are still many limitations and flexibility is still lacking...