A brief discussion on PHP application architecture_PHP tutorial

Although the name is "PHP Best Practices", it mainly talks about not programming rules, but the reasonable architecture of PHP applications.

It provides an architectural pattern that separates logic and data, and is a practice of the MVC pattern. I think this is a valuable learning material. There are not many similar articles online, so I translated it while studying.

Based on my own understanding, I summarized the implementation of its MVC pattern (see translation for detailed explanation):

* View layer (View): front-end web page;

* Logic layer (Controller): First, the page logic (Page Controller) is responsible for processing page requests; then, the business logic (Business Controller) is called to implement specific functions;

* Data layer (Model): Data is stored in the database, with a database abstraction layer above it, and above it is a "data access object" (DAO), which generates a "value object". Business logic operates value objects through DAO.

========================================

PHP best practices

Original: http://www.odi.ch/prog/design/php/guide.php

Translator: Ruan Yifeng

This article gives solutions to common problems in PHP programming and briefly describes the architecture of PHP applications.

　1. php.ini settings

php.ini controls the behavior of the interpreter. The following settings ensure the maximum portability of your program.

i. short_open_tag

Set to 0, which means that PHP's long tag form will always be used: and the short tag form will not be used.

ii. asp_tags

Set to 0 to not use ASP tags.

iii. magic_quotes_gpc

It is recommended to include a global file in the script, which is responsible for checking whether this setting is turned on before reading the $_GET, $_POST, and $_COOKIE variables. If it is turned on, apply the stripslashes function to these variables. (Note: This setting has been deprecated in PHP 5.3.)

iv. register_globals

Don’t rely on this setting. Always read the values ​​of GET, POST and COOKIE through the global variables $_GET, $_POST and $_COOKIE. For convenience, it is recommended to declare $PHP_SELF = $_SERVER[PHP_SELF].

v. file_uploads

The maximum size of uploaded files is determined by the following settings:

* file_uploads must be set to 1 (default value), indicating that uploading is allowed.

* memory_limit must be slightly larger than post_max_size and upload_max_filesize.

* post_max_size and upload_max_filesize must be large enough to meet the upload needs.

　2. Configuration file

You should write all configuration related to the application in a file. This way you can easily adapt to changes in the development environment. Configuration files usually contain the following information: database parameters, email addresses, various options, debug and logging output switches, and application constants.

　3. Namespace

When choosing class and function names, you must be very careful to avoid duplicate names. Try not to place global functions outside the class. The class is equivalent to a layer of namespace protection for the internal properties and methods. If you really need to declare a global function, use a prefix, such as dao_factory(), db_getConnection(), text_parseDate(), etc.

　4. Database abstraction layer

PHP does not provide general functions for database operations. Each database has its own set of functions. You should not use these functions directly, otherwise you will be in trouble once you switch to another database (such as from MySQL to Oracle). Moreover, the database abstraction layer is usually easier to use than the database functions of the system itself.

　5. "Value Object" (Value Object, VO)

Value object (VO) is formally like the struct structure of C language. It is a class that contains only properties and no methods (or very few methods). A value object corresponds to an entity. Its properties should usually remain the same as the database field names. Additionally, there should be an ID attribute.

class Person {

　var $id, $first_name, $last_name, $email;

　}

　6. Data Access Object (DAO)

The role of Data Access Object (DAO) is mainly to isolate database access from other code. DAO should be stacked, which will help you add database caching in the future. Each value object class should have its own DAO.

class PersonDAO {

var $conn;

Function PersonDAO(&$conn) {

$this->conn =& $conn;

　}

Function save(&$vo) {

　if ($v->id == 0) {

$this->insert($vo);

　} else {

$this->update($vo);

　}

　}

Function get($id) {

　#execute select statement

　#create new vo and call getFromResult

　#return vo

　}

Function delete(&$vo) {

　#execute delete statement

　#set id on vo to 0

　}

　#-- private functions

Function getFromResult(&vo, $result) {

　#fill vo from the database result set

　}

Function update(&$vo) {

　#execute update statement here

　}

Function insert(&$vo) {

　#generate id (from Oracle sequence or automatically)

　#insert record into db

　#set id on vo

　}

　}

http://www.bkjia.com/PHPjc/486028.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/486028.htmlTechArticleAlthough the name is "PHP Best Practices", it mainly talks about not programming rules, but PHP applications reasonable structure. It provides an architectural pattern that separates logic and data, belonging to...