Jump to content

Recommended Posts

Like most things, it's neither all good or all bad.  Any benefits gained by flushing the buffer are dependent on what kind of architecture you're using.  You won't see much benefit in an OOP/MVC environment, for example, as all processing is done before anything is rendered.  Flushing, in that case, is pointless as the only logic left to perform at that stage would be simple view logic - conditionals (if/else) and loops.

 

Also, depending on where you flush (most people recommend at the <head> of the document), you'll remove the ability to use HTTP headers, including redirection headers.

 

All in all, it seems like the kind of micro-optimization that may be better addressed through caching and compression.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.