Re: implicit flush feature is fixed => CLI behavior is
| From: | Derick Rethans | Date: | Thu, 03 Oct 2002 10:08:39 +0000 |
| Subject: | Re: implicit flush feature is fixed => CLI behavior is | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-88949@lists.php.net to get a copy of this message | ||
On Thu, 3 Oct 2002, Yasuo Ohgaki wrote:
> Yasuo Ohgaki wrote:
> > Edin Kadribasic wrote:
> >
> >>Again, CLI does nothing but enable implicit_flush. Try enabling it
> >>in your php.ini and cgi and apache will be broken in the same way.
> >>
> >
> >
> > I'll take a look at CLI SAPI, then...
> > It may be easy to find what's wrong thanks to your example.
> >
> > User shouldn't enable implicit_flush for normal operation
> > as commentted for a long time. It's only for debugging.
> >
> > User should use use ob_implicit_flush() instead.
>
> Fixed.
This was not a fix, it was correct before you did this commit.
>
> >From current php.ini-dist
>
> ; Implicit flush tells PHP to tell the output layer to flush itself
> ; automatically after every output block. This is equivalent to calling the
> ; PHP function flush() after each and every call to print() or echo()
> and each
> ; and every HTML block. Turning this option on has serious performance
> ; implications and is generally recommended for debugging purposes only.
Output Layer != Output Buffering, read again what zeev wrote, as he
explained it very well (two times).
Derick
--
---------------------------------------------------------------------------
Derick Rethans http://derickrethans.nl/
JDI Media Solutions
--------------[ if you hold a unix shell to your ear, do you hear the c? ]-