Analyzing Output Buffering in PHP_PHP Tutorial
Let’s look at a piece of code first:
〈?php
for ($i=10; $i〉0; $i--)
{
echo $i;
flush();
sleep(1);
}
?〉
According to the PHP manual, this function sends all the output of the program so far to the user's browser.
The above code should output $i every one second. But this is not necessarily the case in practice. It is possible that after waiting for 10 seconds, all output is presented at the same time.
OK, let’s change this code to
〈?php
ob_end_clean();//Modify part
for ($i=10; $i 〉0; $i--)
{
echo $i;
flush();
sleep(1);
}
?〉
Hey, added This sentence ob_end_clean(); is actually OK. In fact, it is also OK if we replace ob_end_clean() with ob_end_flush().
I will change it again.
〈?php
for ($i=10; $i〉0; $i--)
{
echo $i;
ob_flush();//Modify Part
flush();
sleep(1);
}
?〉
Run it, do you find that $i is also output every second? Why is this?
Don’t worry, let’s take a look at php.ini.
Open php.ini, search for output_buffering, we will see a setting like this output_buffering = 4096. Just like its name output_buffering, the function of this setting is to buffer the output. The buffer size is 4096bytes.
In our first piece of code, the reason why the output is not as expected is precisely because of this output_buffering Buffer those outputs. The output will not be sent before 4096 bytes is reached or the script ends.
The function of ob_end_clean() and ob_end_flush() in the second piece of code is to terminate the buffering. In this way, there is no need to wait until there is a buffer of 4096 bytes before being sent out.
In the third piece of code, ob_flush() is used. Its function is to send the buffered data, but it does not terminate the buffering, so it must be used before each flush().
If we don’t want to use ob_end_clean(), ob_end_flush() and ob_flush(), we must set the output_buffering in php.ini small enough, for example, set to 0. It should be noted that if you plan to use ini_set("output_buffering", "0") to set it in a script, then please stop, this method will not work. Because at the beginning of the script, the buffering settings have been loaded, and then buffering starts.
You may ask, since ob_flush() sends the buffered data, why do you need to use flush()??? Can't you just use the following code? ?
〈?php
for ($i=10; $i〉0; $i--)
{
echo $i;
ob_flush();
sleep(1);
}
?〉
Please note the difference between ob_flush() and flush(). The former is to release data from PHP's buffer, and the latter is to send data that is not in the buffer or has been released to the browser. So when the buffer exists, we must use ob_flush() and flush() at the same time.
Is flush() indispensable here? No, we have another method so that when data is output, it is immediately sent to the browser. The following two pieces of code do not need to use flush().(When you set output_buffering to 0, you don’t even need ob_flush() and ob_end_clean())
?php
ob_implicit_flush(true);
for ($i=10 ; $i〉0; $i--)
{
echo $i;
ob_flush();
sleep(1);
}
?〉
〈 ?php
ob_end_clean();
ob_implicit_flush(true);
for ($i=10; $i〉0; $i--)
{
echo $i;
sleep(1); In this way, there is no need to use flush() to send it to the browser after each output (echo).
The above complaint may not be true in some browsers. Because browsers also have their own rules. I used Firefox1.5, IE6, opera8.5 to test. Among them, opera cannot output normally because it has a rule that if it does not encounter an HTML tag, it will never output unless the script ends. FireFox and IE are relatively normal.
Finally, here is a very interesting piece of code written by PuTTYshell. In a script cycle, each output will overwrite the previous output.
The following code is only available under firefox. Other browsers do not support the Content-Type of multipart/x-mixed-replace.
〈?php
header('Content-type: multipart/ x-mixed-replace;boundary=endofsection');
print “n--endofsectionn“;
$pmt = array(“-“, “\“, “|“, “/“) ;
for( $i = 0; $i 〈10; $i ++ ){
sleep(1);
print “Content-type: text/plainnn“;
print “Part $it".$pmt[$i % 4];
print "--endofsectionn";
ob_flush();
flush();
}
print "Content-type: text/plainnn";
print "The endn";
print "--endofsection--n";
?〉

ThesecrettokeepingaPHP-poweredwebsiterunningsmoothlyunderheavyloadinvolvesseveralkeystrategies:1)ImplementopcodecachingwithOPcachetoreducescriptexecutiontime,2)UsedatabasequerycachingwithRedistolessendatabaseload,3)LeverageCDNslikeCloudflareforservin

You should care about DependencyInjection(DI) because it makes your code clearer and easier to maintain. 1) DI makes it more modular by decoupling classes, 2) improves the convenience of testing and code flexibility, 3) Use DI containers to manage complex dependencies, but pay attention to performance impact and circular dependencies, 4) The best practice is to rely on abstract interfaces to achieve loose coupling.

Yes,optimizingaPHPapplicationispossibleandessential.1)ImplementcachingusingAPCutoreducedatabaseload.2)Optimizedatabaseswithindexing,efficientqueries,andconnectionpooling.3)Enhancecodewithbuilt-infunctions,avoidingglobalvariables,andusingopcodecaching

ThekeystrategiestosignificantlyboostPHPapplicationperformanceare:1)UseopcodecachinglikeOPcachetoreduceexecutiontime,2)Optimizedatabaseinteractionswithpreparedstatementsandproperindexing,3)ConfigurewebserverslikeNginxwithPHP-FPMforbetterperformance,4)

APHPDependencyInjectionContainerisatoolthatmanagesclassdependencies,enhancingcodemodularity,testability,andmaintainability.Itactsasacentralhubforcreatingandinjectingdependencies,thusreducingtightcouplingandeasingunittesting.

Select DependencyInjection (DI) for large applications, ServiceLocator is suitable for small projects or prototypes. 1) DI improves the testability and modularity of the code through constructor injection. 2) ServiceLocator obtains services through center registration, which is convenient but may lead to an increase in code coupling.

PHPapplicationscanbeoptimizedforspeedandefficiencyby:1)enablingopcacheinphp.ini,2)usingpreparedstatementswithPDOfordatabasequeries,3)replacingloopswitharray_filterandarray_mapfordataprocessing,4)configuringNginxasareverseproxy,5)implementingcachingwi

PHPemailvalidationinvolvesthreesteps:1)Formatvalidationusingregularexpressionstochecktheemailformat;2)DNSvalidationtoensurethedomainhasavalidMXrecord;3)SMTPvalidation,themostthoroughmethod,whichchecksifthemailboxexistsbyconnectingtotheSMTPserver.Impl


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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SublimeText3 Chinese version
Chinese version, very easy to use

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Zend Studio 13.0.1
Powerful PHP integrated development environment

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
