Advantages and disadvantages of qeephp and CI
With qeephp do a few projects, suddenly want to learn a new framework, feeling CI is good, do not know the advantages and disadvantages between them, I hope everyone speak freely, there is a good framework to recommend a line.
------Solution--------------------
CI is relatively simple, quick to get started, complete Chinese documents, the following are the main advantages of CI:
What is CodeIgniter?
CodeIgniter is an application framework
CodeIgniter is a toolkit for people who write Web applications in PHP. Its goal is to enable you to develop projects faster than you can write code from scratch, and for this reason, CI provides a rich set of class libraries to meet the usual task requirements, and provides a simple interface and logical structure to invoke these libraries. CodeIgniter can minimize the amount of task code that needs to be done, so you can put more effort into project development.
CodeIgniter is free.
CodeIgniter is licensed by the Apache/bsd-style Open source license and can be used if you wish. Read the license agreement to get more information.
CodeIgniter running on PHP 4
CodeIgniter is fully compatible with PHP 4. Although PHP 5 is more advantageous in object-oriented processing, we should have used this advantage to simplify our creative solution (for example, multi-inheritance) work, but when we built this framework, PHP 5 was not widely used, which means (if written in PHP 5来) PHP4 We are going to abandon most of the potential users. Mainstream operating system vendors such as REDHAT are very slow to turn to PHP5 support, and they are unlikely to fully support PHP5 in the short term. Therefore, we think that PHP 5来 write CodeIgniter not the best interests of the PHP community.
Note: CodeIgniter is capable of running in a PHP5 environment. It's just that it doesn't use advanced features unique to PHP5.
CodeIgniter is lightweight.
The real lightweight. Our core system requires only a few very small libraries, which are the exact opposite of those that require more resources. The additional library files are loaded only at the request, so the core system is very fast and light, depending on the requirements.
CodeIgniter is fast.
The speed is very fast. It should be difficult to find a framework that is better than CodeIgniter.
CodeIgniter using the M-V-C model
CodeIgniter uses the model-view-Controller (Controllers) approach to better decouple the presentation layer from the logical layer. This is very useful for the project's template designer, which minimizes the amount of program code in the template. We have introduced this in more detail in the respective pages of MVC.
CodeIgniter Generate a clean URL
The URLs generated by CodeIgniter are very clean and friendly to search engines. Unlike the standard "string query" method, CodeIgniter uses a method such as segment-based:
example.com/news/article/345
Note: The index.php file is included by default in the URL, but you can change this setting by changing the. htaccess file.
CodeIgniter features Powerful
CodeIgniter has a full range of class libraries that can perform most of the network development tasks typically required, including reading databases, sending e-mails, confirming data, saving sessions, manipulating images, and supporting XML-RPC data transfer.
The CodeIgniter is extensible
This system can be easily extended through plugins and helper libraries, or it can be implemented by extension classes, system hooks, and so on.
CodeIgniter does not require a template engine
Although CodeIgniter does bring an optional template parser program, it does not require that you have to use a template. The template engine is completely inconsistent with the performance requirements of the localized PHP code, and using the template engine we have to learn its syntax, which is at least a little easier than learning PHP basics. Consider the following PHP code:
Then compare the pseudo-code used by the template engine:
{foreach from= $addressbook item= "name"}
- {$name}
{/foreach}
Indeed, the code for the template engine in the example is clear, but this presents a performance problem because the pseudo-code must first be converted to PHP to run. Our goal is to maximize performance, so we choose not to use a dedicated template engine.
CodeIgniter has been thoroughly documented
Programmers like to write code and hate to write documents. Of course we are the same, but since the document is as important as the code itself, we are going to finish it. Moreover, our code resources are extremely clean and easy to annotate.
CodeIgniter has a friendly user community
You can see a growing, active community of users in our community forums.
------Solution--------------------
qeephp data model is more rigid, in order to Oo and OO, rather than for database query optimization.
For example, every time it will query the table structure .....
And not like
------Solution--------------------
CI compatible PHP4, the Chinese document comparison is complete. In the model layer design than cakephp almost
------Solution--------------------
Because it needs to have a database is a map, so there must be a table structure! Then build the Model Object!
It's the same as cakephp!
But CI and zendframe don't do this, especially zendframe!.
It believes that the database model does not have to do table mapping!
Instead, the database model should be based on business logic! (This is faster)
Related to this is also the form validation, some in the model class, and some in the Controller method!
For example: Zend is in the Controller Method! (This is also because some validations may not be related to the database, or to multiple tables)
------Solution--------------------
CI quick function Full but not suitable for large sites
