Why use output buffering in PHP?
I have read quite a bit of material on Internet where different authors suggest using output buffering. The funny thing is that most authors argument for its use only because it allows for mixing response headers with actual content. Frankly, I think that responsible web applications should not mix outputting headers and content, and web developers should look for possible logical flaws in their scripts which result in headers being sent after output has been generated. This is my first argument against the ob_* output buffering API. Even for that little convenience you get - mixing headers with output - it is not a good enough reason to use it, unless one needs to hack up scripts fast, which is usually not the goal nor the way in a serious web application.
Also, I think most people dealing with the output buffering API do not think about the fact that even without the explicit output buffering enabled, PHP in combination with the web-server it is plugged into, still does some internal buffering anyway. It is easy to check - do an echo of some short string, sleep for say 10 seconds, and do another echo. Request your script with a browser and watch the blank page pause for 10 seconds, with both lines appearing thereafter. Before some say that it is a rendering artefact, not traffic, tracing the actual traffic between the client and the server shows that the server has generated the Content-Length header with an appropriate value for the entire output - suggesting that the output was not sent progressively with each echo call, but accumulated in some buffer and then sent on script termination. This is one of my gripes with explicit output buffering - why do we need two different output buffer implementations on top of one another? May it be because the internal (inaccessible) PHP/Web-server output buffering is subject to conditions a PHP developer cannot control, and is thus not really usable?
In any case, I for one, start to think one should avoid explicit output buffering (the series of ob_* functions) and rely on the implicit one, assisting it with the good flush function, when necessary. Maybe if there was some guarantee from the web server to actually send output to the client with each echo/print call, then it would be useful to set up explicit buffering - after all one does not want to send response to the client with some 100 byte chunks. But the alternative with two buffers seems like a somewhat useless layer of abstraction.
So, ultimately, do serious web applications need output buffering?
Yes
Serious web applications need output buffering in one specific situation:
Your application wants control over what is output by some 3rd-party code, but there is no API to control what that code emits.
In that scenario, you can call ob_start() just before handing control to that code, mess around with what is written (ideally with the callback, or by examining the buffer contents if you must), and then calling ob_flush() .
Ultimately, PHPs' ob_functions are a mechanism for capturing what some other bit of code does into a buffer you can mess with .
If you don't need to inspect or modify what is written to the buffer, there is nothing gained by using ob_start() .
Quite likely, your 'serious application' is in fact a framework of some kind.
You already have output buffering, anyway
You don't need ob_start() in order to make use of output buffering. Your web-server already does buffer your output.
Using ob_start() does not get you better output buffering - it could in fact increase your application's memory usage and latency by 'hoarding' data which the web-server would otherwise have sent to the client already.
Maybe ob_start() ...
... for convenience when flushing
In some cases, you may want control over when the web-server flushes its buffer, based on some criteria which your application knows best. Most of the time, you know that you just finished writing a logical 'unit' which the client can make use of, and you're telling the web-server to flush now and not wait for the output buffer to fill up. To do this, it is simply necessary to emit your output as normal, and punctuate it with flush() .
More rarely, you will want to withhold data from the web-server until you have enough data to send. No point interrupting the client with half of the news, especially if the rest of the news will take some time to become available. A simple ob_start later concluded by an ob_end_flush() may indeed be the simplest and appropriate thing to do.
... if you have responsibility for certain headers
If your application is taking responsibility for calculating headers which can only be determined after the full response is available, then it may be acceptable.
However, even here, if you can't do any better than deriving the header by inspecting the complete output buffer, you might as well let the web-server do it (if it will). The web-server's code, is written, tested, and compiled - you are unlikely to improve on it.
For example, it would only be useful to set the Content-Length header if your application knows the length of the response body after before it computes the response body.
No panacea for bad practices
You should not ob_start() to avoid the disciplines of:
If you do these, they will cause technical debt which will make you cry one day.
Ok, here is the real reason : the output is not started until everything is done. Imagine an app which opens an SQL connection and doesn't close it before starting the output. What happens is your script gets a connection, starts outputting, waits for the client to get all it needs then, at the end, closes the connection. Woot, a 2s connection where a 0.3s one would be enough.
Now, if you buffer, your script connects, puts everything in a buffer, disconnects automatically at the end, then starts sending your generated content to the client.
如果您想要将报告输出到屏幕并通过电子邮件发送，则输出缓冲功能可让您不必重复处理以输出报告两次。
链接地址: http://www.djcxy.com/p/34686.html上一篇: 是否使用输出缓冲被认为是一种不好的做法？
下一篇: 为什么在PHP中使用输出缓冲？