Comments on: Don’t Forget to Flush

By: Michael Caplan

Michael Caplan — Wed, 12 Oct 2011 13:49:31 +0000

On load event handlers will only be processed after the complete page has been loaded. jQuery’s .ready() (http://api.jquery.com/ready/) method is probably a better choice if you are just interacting with DOM nodes.

By: OnLine

OnLine — Wed, 12 Oct 2011 10:31:21 +0000

Hi
For example, if in the HEAD section i have a javascript with an window.onload instruction that selects some html elements from body, then i call flush() before the BODY.
This will send the HEAD code to browser, but if the BODY isn’t added in that moment, doesn’t it affect the JavaScropt code.
Or, the window.onload will know and wait till the whole html page is loaded?

By: Michael Caplan’s Blog: Don’t Forget to Flush : Dragonfly Networks

Michael Caplan’s Blog: Don’t Forget to Flush : Dragonfly Networks — Fri, 09 Jan 2009 10:58:27 +0000

[...] this recent post to his blog Michael Caplan looks at a feature of PHP that’s sometimes forgotten when pushing [...]

By: Mikael

Mikael — Wed, 07 Jan 2009 11:54:06 +0000

Whoops, missed the last paragraph… sorry !

By: Mikael

Mikael — Wed, 07 Jan 2009 11:52:24 +0000

I love the idea, but that is probably not gonna work in most MVC frameworks that implement the ‘two-step’ view way of rendering views.

As an example with ZF, as Loïc mentionned: if you use Zend_Dojo or Zendx_jQuery in conjunction with Zend_Layout, you don’t build the HEAD content in one single spot in your code. It is done in several places, and this makes it hard to use a flush.

Example:
- Take a random, database-heavy page that is included in a default layout (= template). This is where most of the computing time is spent. That page then decides it needs some obscure plugin js file. That page is rendered. So far you can’t send anything to the client.
- Then the layout decides that it needs a general use JS library. The layout is rendered and it then includes (wraps) the previously rendered page.
All work is done, the full response (head + body) are computed and can be sent back to the client. Nowhere in this scenario could you do a flush.

I’d love to hear a solution to this (or maybe I’m plain wrong ?), because this sounds like it could really speed up JS heavy webpages.

By: Loïc Hoguin

Loïc Hoguin — Mon, 05 Jan 2009 10:15:24 +0000

About nested templates, I’m not sure about ZF but you could probably have a header template that you would create and render as soon as you receive the request, and then have a body template that would contain the rest. The HTML header usually doesn’t have too much specific code so it should work out pretty well for most projects.

By: ellisgl

ellisgl — Mon, 05 Jan 2009 02:50:27 +0000

Beware of using flush by itself. Some times you have to make sure that you have enough data output before the browser response. Here’s something I’ve been using with my COMET stuff.

function RealFlush($Out = “”, $Padding = 4096)
{
echo str_pad($Out, $Padding);
@ob_flush();
@flush();
}