Working principle of PHP underlying layer

The Apach request processing process in the article directory was recently set up a server. Suddenly, how does lamp work or how does it work? I usually only write programs, but I have never thought about the working principle between them: the underlying Working Principle of PHP. The php structure shows from the figure that php is a layer-4 system from bottom to top. ① Zend engine Zend

The Apach request processing process in the article directory was recently set up a server. Suddenly, how does lamp work or how does it work? I usually only write programs, but I have never thought about the working principle between them: the underlying Working Principle of PHP. The php structure shows from the figure that php is a layer-4 system from bottom to top. ① Zend engine Zend

Document directory

• Apach request processing process

Recently, when I set up a server, I suddenly felt how lamp works or how it works? I usually write programs and never think about how they work:

Working principle of PHP underlying layer

Php Structure

From the figure, we can see that php is a layer-4 system from bottom to top.

① Zend Engine

Zend is implemented in pure c and is the kernel part of php. It translates php code (a series of compilation processes such as lexical and Syntax Parsing) it can process and implement corresponding processing methods, implement basic data structures (such as hashtable and oo), allocate and manage memory, and provide corresponding api methods for external calls, is the core of everything, and all peripheral functions are implemented around zend.

② Extensions

Around the zend engine, extensions provides various basic services in a component-based manner. Our common built-in functions (such as the array series) and Standard libraries are implemented through extension, you can also implement your own extension as needed to achieve function expansion and performance optimization (for example, the php middle layer being used by the post bar and Rich Text parsing are typical applications of extension ).

③ Sapi

The full name of Sapi is the Server Application Programming Interface, that is, the Server Application Programming Interface. sapi enables php to interact with peripheral data through a series of hook functions, which is a very elegant and successful design of php, through sapi, php itself and upper-layer applications are successfully decoupled and isolated. php can no longer consider how to be compatible with different applications, and the application itself can implement different processing methods based on its own characteristics. This topic will be introduced later in sapi

④ Upper-layer applications

This is the php program we usually write and various application modes are obtained through different sapi methods, such as implementing web applications through webserver and running scripts under the command line.

Architecture:

Engine (Zend) + component (ext) mode reduces internal coupling

The middle layer (sapi) isolates web server and php

**************************************** **********************************

If php is a car

The car's framework is php itself.

Zend is a car engine)

The components below Ext are the wheels of a car.

Sapi can be seen as a highway, and vehicles can run on different types of Roads

The execution of a php program is that a car runs on the road.

Therefore, we need an engine with excellent performance + a proper wheel + a correct runway.

Relationship between Apache and php

Apache's php Parsing is done through the php Module in many modules.

To integrate php into Apache, you also need to make some necessary settings for Apache. Here, we will take the mod_php5 SAPI running mode of php as an example. The SAPI concept will be explained in detail later.

Assume that the installed versions are Apache2 and Php5. Edit the main configuration file http. conf of Apache and add the following lines to it:

In Unix/Linux:

LoadModule php5_module modules/mod_php5.so

AddType application/x-httpd-php. php

Note: modules/mod_php5.so is the installation location of the mod_php5.so file in the X system environment.

In Windows:

LoadModule php5_module d:/php/php5apache2. dll

AddType application/x-httpd-php. php

Note: d:/php/php5apache2. dll is the installation location of the php5apache2. dll file in Windows.

These two configurations tell the Apache Server that any Url user request received later uses php as the suffix and needs to be processed by calling the php5_module module (mod_php5.so/php5apache2. dll.

Apache Lifecycle

Apach request processing process

Detailed explanation of Apache request processing cycle
What have been done in the 11 phases of Apache request processing cycle?

1. Post-Read-Request stage

In the normal request processing process, this is the first stage in which the module can insert hooks. This phase can be used by modules that want to process requests very early.

2. URI Translation stage
Apache's main work in this phase: map the request URL to the local file system. The module can insert hooks at this stage to execute its own ing logic. Mod_alias uses this phase of work.

3. Header Parsing stage
In this phase, Apache checks the request header. This hook is rarely used because the module can execute the task of checking the request header at any point in the request processing process. Mod_setenvif uses this phase of work.

4. Access Control stage
Apache's main work in this phase: Check whether the requested resources are allowed to be accessed Based on the configuration file. Apache's Standard logic allows and denies commands. Mod_authz_host is used in this phase.

5. Authentication stage
Apache's main work in this phase: authenticate users according to the policies set in the configuration file, and set the user name area. The module can insert hooks at this stage to implement an authentication method.

6. Authorization stage
Apache's main work in this phase: checks whether Authenticated Users are allowed to perform request operations based on the configuration file. The module can insert hooks at this stage to implement a user permission management method.

7. MIME Type Checking stage
Apache's main work in this phase: determine the content processing functions to be used based on the rules related to the MIME type of the requested resource. The standard modules mod_negotiation and mod_mime implement this hook.

8. FixUp stage
This is a common stage that allows a module to run any necessary processing flow before the content generator. Similar to Post_Read_Request, This Is A hook that can capture any information and is also the most commonly used hook.

9. Response stage
Apache's main work in this phase: generate the content returned from the client and send an appropriate response to the client. This stage is the core part of the entire processing process.

10. Logging stage
Apache's main work in this phase: record transactions after replying to a client. The module may modify or replace Apache standard logging.

11. CleanUp stage
The main work of Apache in this phase: clean up the environment left after the transaction processing of this request is completed, such as processing files, directories, or closing Socket, etc, this is the last stage of Apache request processing.

LAMP architecture:

From bottom to top 4:

① Liunx is the underlying operating system

② Apache server, which belongs to the secondary server, communicates with linux and PHP

③ Php: it belongs to the server programming language and is associated with apache through the php_module module.

④ Mysql and other web Services: it is an application service. It is associated with mysql through the Extensions external modules of PHP.

Android Architecture

The lamp and Android architecture diagram is similar to the lamp architecture. I don't know about Android, but I feel a little similar. Experts can point out the differences. Thank you very much.

From top to bottom:

Android architecture ----- description --- LAMP Architecture

1. Application --- specific application --- web Application

2. Application Framework-java ----- PHP language and Library

3. System Runtime Library: -- virtual machine --- WEB Server

Customized Linux kernel:-operating system --- L in lamp Architecture

Relationship between lamp and the computer

CPU is a factory, hard disk is a large warehouse, memory is a regular transit center, and virtual memory is a temporary transit center

The Php language is compiled from zend to machine language to operate the cpu.

Database Operations are I/O operations and mechanical operations. That is to say, a website bottleneck causes hard disk read/write operations. The solution is to reduce the number of I/o operations, the buffer technology is used to store data operations in the mencache, and write data to the database at a time when it reaches a certain order of magnitude. The mencache belongs to the key-value relationship.

Not relational data is built based on this concept, but also belongs to the key-value relationship.

Frequent read operations-placed in mencache

Read, write, and less-Put It In nosql-the reading function is very powerful!