PHP output_buffering How much do you know, phpoutputbuffering_PHP tutorial

PHP output_buffering How much do you know about phpoutputbuffering

1. Let’s talk about what are the caches in php!

In PHP, we can roughly divide cache into client cache (Browser cache) and server cache (Server cache). Since PHP is based on B/S architecture, we can understand it as browser-side cache and server-side cache.
In the cache that comes with PHP on the server side, it can be divided into two main types of cache! Program cache and OB cache! This is also the main content for us to learn server-side caching!

The cached output sequence in PHP is:

Open php output buffer: echo,print -> php output_buffering -> server buffering -> browser buffering -> browser display

PHP output cache is not turned on: echo,print -> server buffering -> browser buffering -> browser display

Browser output cache: 256Bytes for IE, 1000Bytes for Chrome and FireFox. Only when the output data reaches this length or the script ends, the browser will output the data on the page.

2. Server-side response process

A. The client sends a request response to the server!
B. The Apache server loads the PHP module, starts the corresponding process (or thread) and runs the corresponding PHP script page!
C. When OB cache is not turned on, all running results will be placed in the program cache, and then packaged and sent to the browser! The browser renders the page and generates the WEB page we last saw!
D. When the OB cache is turned on, the running results will be put into the OB cache and the program cache respectively. When the program runs to the last line, the data in the OB cache will be flushed back The program is cached and then packaged and returned to the browser! The browser renders the page and generates the WEB page we see!

3. Common uses of OB cache!

a, output_buffering=4096, output less data (less than one buffer)

for($i=0; $i<5; $i++){  

echo $i.'<br>';  

sleep(1);  

}

Run results: Output only after all scripts are completed, because the data is not full of one buffer size.

b, output_buffering=4096, output less data (less than one buffer), turn off output_buffering, modify output_buffering=0 in php.ini

echo str_repeat(" ",1024);//这里重复输出一个空白

for($i=0; $i<5; $i++){  

echo $i."<br/>";

    flush();  

    sleep(1);  

} 

Running result: Because OB is disabled, there is no need to wait for the script to run before it can be output. The data does not stay in the OB, and you can see intermittent output. echo ->browser buffering -> browser display

c, output_buffering=4096, output larger data (larger than one buffer), do not use ob_start()

for($i=0; $i<5; $i++){  

    echo file_get_contents('f.txt').$i.'<br/><br/><br/><br/>';  

    sleep(2);  

} 

Running result: f.txt is a file larger than 4kb. Because it is larger than the default value of the buffer, the buffer space is not enough. It will be output every time the buffer is full, so you can see intermittent output.

d, output_buffering=4096, output larger data (larger than one buffer), use ob_start()

ob_start();  

for($i=0; $i<5; $i++){  

    echo file_get_contents('f.txt').$i.'<br/><br/><br/><br/>';  

    sleep(2);  

} 

Running result: Because ob_start() is used, a large enough space will be set for the buffer, so it will be saved until the script is executed and then output.

e, output_buffering=On, use ob_start()

ob_start(); 

echo "abc-";

header("content-type:text/html;charset=utf-8");

echo "hello-";

ob_end_flush();

echo "aa-";

echo ob_get_contents();

Run result: abc-hello-aa-abc-hello-aa-

f, output_buffering=Off, use ob_start()

ob_start(); 

echo "abc-";

header("content-type:text/html;charset=utf-8");

echo "hello-";

ob_end_flush();

echo "aa-";

echo ob_get_contents();

Run result: abc-hello-aa-

Output buffers are stackable, which means that when one ob_start() is active, you can call another ob_start(). Just make sure you call ob_end_flush() correctly the appropriate number of times. If multiple output callback functions are active, the output content will always be filtered through them in nested order.

Note: In PHP5.2, OB is turned off by default, and after 5.3 it is turned on by default;

Common methods:

1.ob_start
Activate the output_buffering mechanism. Once activated, the script will no longer be output directly to the browser, but will be temporarily written to the php buffering area. It is not sent until the script has finished running.

2.ob_get_contents
Get the data in php buffering. Note: it must be called before ob_end_clean(), otherwise you will only get empty characters.

3.ob_end_flush and ob_end_clean
ob_end_flush will output the data in php buffering, but will not clear it.
ob_end_clean will not output, it will only clear the data in php buffering.

4.ob_flush, flush, ob_implicit_flush
ob_flush will refresh the data in php buffering to the program cache

flush will refresh the program cache into the browser cache

ob_implicit_flush will turn absolute (implicit) flushing on or off. An absolute (implicit) flush will result in a flush operation after each output call so that explicit calls to flush() are no longer needed

4. The role of OB cache!

OB cache is used in various aspects, but what I know is mainly in two aspects!
a. When the website is going to be staticized, choosing OB cache is a good choice!

b. Solve the error of Warning: Cannot modify header information - headers already sent by!
The reason for the error: it is caused by the misalignment of the response header and the corresponding body! Under normal circumstances, the corresponding content returned by the server to the browser should be: response header response body!
However, if we enable OB cache, then the corresponding header information (generally the information set by the header() function) will be placed in the program cache!
Other output content, such as: echo print_r var_dump, etc., will be put into the OB cache first!
When the program ends, or the OB cache is closed, put the contents of the OB cache into the program cache! This ensures that the response header information always precedes the response body content!

5. Reference materials:

http://segmentfault.com/a/1190000000578885

http://blog.csdn.net/fdipzone/article/details/10367837

http://php.net