perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: $|, flushing, etc... [was Next Release]
Date Tue, 04 Oct 2005 17:45:53 GMT
Philip M. Gollucci wrote:
> 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.

and if you try my last patch suggestion?

-- 
_______________________________________________________________
Stas Bekman mailto:stas@stason.org   | http://stason.org/
MailChannels: Assured Messaging (TM) | http://mailchannels.com/
The "Practical mod_perl" book        | http://modperlbook.org/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message