perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip M. Gollucci" <>
Subject Re: $|, flushing, etc... [was Next Release]
Date Tue, 04 Oct 2005 16:22:59 GMT
Stas Bekman wrote:
> As I think more about it, there was a reason for this FALSE setting. As 
> you know Apache will send headers as soon as it gets some data out and a 
> flush bucket is by Apache-talk is data. So what was happening is that 
> when users were doing something in their code that was causing perl to 
> flush STDOUT behind the scenes (like a filehandle dup), Apache will go 
> and generate the headers even if the user haven't had a chance to set 
> those. That's why it was written in such a way: i.e. add a flush bucket 
> only if there is some data to flush, otherwise you need to call 
> $r->flush if you want the flush to be sent anyway.
Yes, it breaks scanhdrs2.t by setting it to TRUE.

     What doesn't kill us can only make us stronger.
                 Nothing is impossible.
Philip M. Gollucci ( 301.254.5198
Consultant /
Senior Developer / Liquidity Services, Inc.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message