Zeev Suraski wrote: > But it does not seem as if you fixed it properly. I don't see how > implicit flush can be at all related to output buffering. If it was, it > should have been trivial to fix it, at a centralized place. You appear > to be adding code all over the codebase, and as far as I understood from > the thread, apparently you also made implicit flush disable output > buffers, which is completely undesired behavior. Please revert! If > there's still an issue with implicit flush after you revert, I will fix it.
Zeev, ob_implicit_flush() and php.ini's implicit_flush never worked for nested output buffers. Why? Older (which is very older now) code before my fix, ob_implicit_flush() and implicit_flush was assuming there is only one buffer always. It caused all kinds of problems due to broken memory. Now, ppl is complaining w/o knowing how implicit flush and output buffer is working. (which I think very rude) For others, implicit_flush in php.ini only for debugging. It may do something unwanted thing in your script, but this is original design. Old code is just deleting buffer to disable buffering. Newer code, which is much better than deleting all buffers, process all buffers and output. implicit_flush should only be used for debugging. If you need implicit flush, use ob_implicit_flush() to have more control. BTW, I think I found what's wrong in CLI thanks to Edin's example. -- Yasuo Ohgaki -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
