[wp-hackers] output buffering in general and wordpress
halukkaramete at gmail.com
Thu May 3 08:31:01 UTC 2012
It's kind of irrelevant but for some reason it seemed appropriate to
me to ask the following right very now.
How about sessions. Can we say the same thing for sessions?
Turn it on or off anytime, no ill effects to WP whatsoever.
On Thu, May 3, 2012 at 1:22 AM, Dion Hulse (dd32) <wordpress at dd32.id.au> wrote:
> WordPress doesn't use it, unless you use a plugin which does (for
> example, a caching plugin).
> WordPress works with it on, or off.
> You can enable it on the fly for pages/sections you need to use it in
> and it'll cause no ill effects to WordPress
> On 3 May 2012 18:18, Haluk Karamete <halukkaramete at gmail.com> wrote:
>> does WP turn on the output_buffering ( or does it not care? - it
>> leaves it up to the php config )
>> And if I do turn it on (for some reason - maybe to get a hold of the
>> entire HTML being sent to the client), does it in any shape or form
>> interfere with the way WP works? In other words, can I just turn it on
>> or off on a page by page basis?
>> On Thu, May 3, 2012 at 12:58 AM, Mike Little <wordpress at zed1.com> wrote:
>>> On Thu, May 3, 2012 at 8:39 AM, Stas Sușcov <stas at nerd.ro> wrote:
>>>> Fyi, I didn't interpret any links, I gave examples on how and when people
>>>> use output buffering. You might agree or not, but thats your opinion.
>>> By associating two of the references with the word "debatable", and one of
>>> them with "mostly not true", you did, indeed interpret them.
>>> There is a reason the lower level 'engines'; apache web server, OS file
>>> handling libraries, etc. do buffering for you (using higher level
>>> languages): it's because they do it best; it's because they hold the
>>> connection to the output stream and know when the pipe is empty and ready
>>> for the next packet of data and when it is busy so output must be buffered.
>>>> Also, there's no such term _general programming_, it's just programming!
>>> There are a number of programming paradigms that are far, far from general
>>> programming: high speed I/O for instance, machine control for another
>>> example (both fields I have worked in), programming where you interface
>>> directly with the hardware; in those instances there might be reasons to
>>> handling your own buffering, and to program in a way that would be odd and
>>> even a little counter-intuitive to many general programmers. However this
>>> is wandering off-topic.
>>> Mike Little
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers