


CI framework source code reading notes 8 Controller.php, cicontroller.php_PHP tutorial
CI framework source code reading notes 8 Controller.php, cicontroller.php
Time has been tight recently, and the source code reading series updates are a bit slow. Since there is relatively little code in Controller, this blog will first update the source code analysis of this file.
After routing and distribution, the actual application Controller takes over all the user's requests and is responsible for interacting with user data. All application controllers in CI should be subclasses of CI_Controller (unless you extend the core of CI, then your Controller parent class can be MY_Controller).
In application controllers, we often use code like this:
/* 加载配置文件 */ $this->load->config("config_app"); /* 加载model */ $this->load->model("user"); /* 加载视图 */ $this->load->view("index"); /* 获取post */ $this->input->post("data",true); /* 获取 get */ $this->input->get("data",true); /* 清除xss */ $this->security->xss_clean($data); /* mark时间点 */ $this->benchmark->mark("app_start");
How are these implemented? Let’s simply follow them next.
Although the structure of this class is very simple, we still post the class diagram of CI_Controller:
1. _construct() constructor
Here CI does a process and adds all loaded components to CI_Controller (we have seen earlier that the is_loaded function tracks all loaded components):
foreach (is_loaded() as $var => $class) { $this->$var =& load_class($class); }
Look at the components tracked by is_loaded when the Controller is instantiated:
This explains why we can call CI components through $this->input and other methods.
This is not enough, let’s also bring in the Loader:
$this->load =& load_class('Loader', 'core'); $this->load->initialize();
Now, you can use the Loader component to load the configuration ($this->load->config) and load the model ($this->load->model ) and load the view ($this->load->view)
CI_Controller can be said to be a super class that holds multiple components. In this way, it is very similar to the "agent pattern" in the design pattern.
2. &get_instance
A brief explanation here is that CI_Controller is a singleton mode class, and an instance of this class is obtained through the get_instance() method. This method is called by the get_instance function in CodeIgniter.php:
public static function &get_instance() { return self::$instance; }
The following are some Hints about Controller:
1. The directory can be customized in the Controller in CI. For example, create the directory admin in the application/controller directory and create a new IndexController. Then the URL access path of the Controller is:
test.xq.com/admin/index/
2. The Controller should not bear too much logic, and the business logic should be encapsulated into the Model.
3. Your Controller should be differentiated according to business. For example, UserController handles user-related requests, while AppController handles application requests. This is not a principle, but just a way.
4. The Controller class name should start with a capital letter, and the file name should be all lowercase.
5. Methods starting with an underscore in the Controller are considered private methods by CI and cannot be directly accessed by the outside.
The above is all the content of Controller.
Finally, the source code of CI_Controller is posted:
class CI_Controller { private static $instance; /** * Constructor */ public function __construct() { self::$instance =& $this; foreach (is_loaded() as $var => $class) { $this->$var =& load_class($class); } $this->load =& load_class('Loader', 'core'); $this->load->initialize(); log_message('debug', "Controller Class Initialized"); } public static function &get_instance() { return self::$instance; } }
References for this article:

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Evaluating the cost/performance of commercial support for a Java framework involves the following steps: Determine the required level of assurance and service level agreement (SLA) guarantees. The experience and expertise of the research support team. Consider additional services such as upgrades, troubleshooting, and performance optimization. Weigh business support costs against risk mitigation and increased efficiency.

The learning curve of a PHP framework depends on language proficiency, framework complexity, documentation quality, and community support. The learning curve of PHP frameworks is higher when compared to Python frameworks and lower when compared to Ruby frameworks. Compared to Java frameworks, PHP frameworks have a moderate learning curve but a shorter time to get started.

The lightweight PHP framework improves application performance through small size and low resource consumption. Its features include: small size, fast startup, low memory usage, improved response speed and throughput, and reduced resource consumption. Practical case: SlimFramework creates REST API, only 500KB, high responsiveness and high throughput

According to benchmarks, for small, high-performance applications, Quarkus (fast startup, low memory) or Micronaut (TechEmpower excellent) are ideal choices. SpringBoot is suitable for large, full-stack applications, but has slightly slower startup times and memory usage.

Writing clear and comprehensive documentation is crucial for the Golang framework. Best practices include following an established documentation style, such as Google's Go Coding Style Guide. Use a clear organizational structure, including headings, subheadings, and lists, and provide navigation. Provides comprehensive and accurate information, including getting started guides, API references, and concepts. Use code examples to illustrate concepts and usage. Keep documentation updated, track changes and document new features. Provide support and community resources such as GitHub issues and forums. Create practical examples, such as API documentation.

Choose the best Go framework based on application scenarios: consider application type, language features, performance requirements, and ecosystem. Common Go frameworks: Gin (Web application), Echo (Web service), Fiber (high throughput), gorm (ORM), fasthttp (speed). Practical case: building REST API (Fiber) and interacting with the database (gorm). Choose a framework: choose fasthttp for key performance, Gin/Echo for flexible web applications, and gorm for database interaction.

In Go framework development, common challenges and their solutions are: Error handling: Use the errors package for management, and use middleware to centrally handle errors. Authentication and authorization: Integrate third-party libraries and create custom middleware to check credentials. Concurrency processing: Use goroutines, mutexes, and channels to control resource access. Unit testing: Use gotest packages, mocks, and stubs for isolation, and code coverage tools to ensure sufficiency. Deployment and monitoring: Use Docker containers to package deployments, set up data backups, and track performance and errors with logging and monitoring tools.

There are five misunderstandings in Go framework learning: over-reliance on the framework and limited flexibility. If you don’t follow the framework conventions, the code will be difficult to maintain. Using outdated libraries can cause security and compatibility issues. Excessive use of packages obfuscates code structure. Ignoring error handling leads to unexpected behavior and crashes.
