--- In exceptional-performance@yahoogroups.com, "gobezu@..." <gobezu@...> wrote:
>
> http://developer.yahoo.com/performance/rules.html#flush
>
> Implementing my upcoming site I have gone through this very helpful set of
guidelines and found myself stack at the point of flushing which I feel,
although is promising considering enhanced user experience, contradicts with
earlier set rules of:
> 1. compression
> 2. content length
>
> These 2 issues among others are also mentioned here:
>
http://stackoverflow.com/questions/352759/php-flush-how-often-and-best-practises\
/352787
>
> So I am now wondering if someone have been able to achieve implementing the
rule of early flushing and still maintained compression, as for content length I
don't see how that can ever be achieved so lets forget that part. If so please
let me know how.
>
> If not, I do believe I make a better choice to prefer compression above
flushing, or any data that might shade light on this issue?
>
> Thanks
>

With "Transfer-Encoding: chunked" header you can send compressed contents in
more parts.

Also, consider using ob_flush() alongside flush() so that the buffered content
is flushed and sent compressed.

It works.