Re: output buffering

It's been a while since I touched that piece of code, so I don't remember how exactly it's supposed to work. However, right now, the URL rewriting code uses output buffering, so it's not too odd that the output is being buffered. Back when I made this change, I used a 4096-byte chunk size (and that's how it works in 4.2), but right now, miraculously, it appears to be using an unlimited buffer size for some reason. Yasuo? A couple of questions for clarity: (a) Does this work properly with PHP 4.2? (b) Other than the buffering issue, does it perform what it's supposed to do (i.e., yields the right output)? Zeev At 06:02 07/10/2002, Sascha Schumann wrote:

    Hi,

    the recent changes in the output buf layer are causing PHP to
    buffer data too aggressively.

    The test case outputs two lines of HTML a few times and
    expects these lines to be immediately forwarded to the url
    scanner.  Regardless of the output_buffering/implicit_flush
    ini settings, the HTML is buffered and does not get to the
    scanner until the script finishes.

    During the script, we change the behaviour of the URL scanner
    by modifying the tags its matching on.  Only the last INI
    setting is applied to the HTML output.  Sprinkling the code
    with flush()es and enabling implicit_flush does not help.

    http://lxr.php.net/source/php4/ext/session/tests/021.phpt

    - Sascha