Zeev Suraski wrote: >> implicit_flush in php.ini only for debugging. >> It may do something unwanted thing in your script, but >> this is original design. > > > As the one who introduced implicit_flush, no, it is not the original > design at all. It's not something for debugging only, but also useful > in certain interactive or report applications, including in the web > environment.
I'm not sure what is your worry. implicit_flush in php.ini is never worked for nested buffers. It was simply deleting OG(active_buffer), which is obviously wrong for nested output buffers. Yes. It may be little different as original intention, but it works as it should. Suppose these are buffer stacked like this lev 2: mb_output_handler lev 1: default buffer New code applies all buffer to each output when implicit_flush is on. It also applies all buffers when user called ob_implicit_flush(). Without buffers, output could be totally useless. > Again, Yasuo, I'm not sure why implicit_flush was related in any way to > output buffering. You say that it was somehow incompatible with multiple > buffers, and I believe you, but fixing it in a way that ties it with > output buffering is wrong, period. Looking at the old code it looks It may not flush as user expected. It is depends on how each buffers treat data. For instance, a handler may need 1024 bytes before output anything. Anyway, I'm not big fun of implicit flush and removing the feature is ok to me, too. -- Yasuo Ohgaki -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
