Re: [PHP-DEV] Re: output buffering problem

Please ask these questions on the php-general list. --Wez. On Thu, 19 Dec 2002, electroteque wrote: > sorry about the false alarm , if you go here u will see a working example > > http://galleries.dyndns.org:1023/progress.php > > i had to add both flush functions together to work , obviosuly fls

[PHP-DEV] Re: output buffering problem

sorry about the false alarm , if you go here u will see a working example http://galleries.dyndns.org:1023/progress.php i had to add both flush functions together to work , obviosuly flsuh is not emptying the buffer within a loop, is this still a bug ? flush(); ob_flush(); "Electroteque" <[EMAI

[PHP-DEV] Re: output buffering problem

actually i singled it out , it doesnt flush until the end of the loop, so it waits till the loop is finished and then flushes i suppose this is a bug. "Electroteque" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > hi guys i have the latest cvs , my function used

Re: [PHP-DEV] Re: output buffering

Zeev Suraski wrote: > > Aha, ok, that actually makes quite a bit of sense. If there's a bit of > output that remains inside the buffers, and the session module gets > deactivated before this output is flushed, we're in trouble... I'll > take a look at it. i think i've been bitten by this us

Re: [PHP-DEV] Re: output buffering

I think we have a bit of a language gap, which is fine, but let's settle for that: Please make sure that if you have a small doubt regarding a certain behavior, especially in a core component of PHP such as the output buffering layer or the session module - you ask the relevant author(s) about

Re: [PHP-DEV] Re: output buffering

Zeev Suraski wrote: > Really? Yasuo, people have been requesting that we disable your write > access to the full php4 tree, and uptil now I was against it. But this > attitude is making me reconsider my stand on this. > > This is the 2nd time in the last couple of days that I notice that your

Re: [PHP-DEV] Re: output buffering

> I understand, but what if you don't call ob_flush()? Does it work properly? The bug from 4.2.3 does not reappear here. The rewriter kicks in using the final combination of ini settings. - Sascha -- PHP Development Mailing List To unsubscribe, visit: http:

Re: [PHP-DEV] Re: output buffering

At 18:43 07/10/2002, Sascha Schumann wrote: >On Mon, 7 Oct 2002, Zeev Suraski wrote: > > > Can you see if calling php_end_ob_buffers() in the session deactivate > > function, in case BG(url_adapt_state_ex).active is true, solves this > problems? > > Note the condition here: > > > > There

[PHP-DEV] Re: output buffering

On Mon, 7 Oct 2002, Zeev Suraski wrote: > Can you see if calling php_end_ob_buffers() in the session deactivate > function, in case BG(url_adapt_state_ex).active is true, solves this problems? Note the condition here: > > There is an even weirder bug, at least in the 4.2.3/CGI case

[PHP-DEV] Re: output buffering

Can you see if calling php_end_ob_buffers() in the session deactivate function, in case BG(url_adapt_state_ex).active is true, solves this problems? Zeev At 12:24 07/10/2002, Sascha Schumann wrote: > > A couple of questions for clarity: > > > > (a) Does this work properly with PHP 4.2? > >

Re: [PHP-DEV] Re: output buffering

At 17:53 07/10/2002, David Reid wrote: >Agreed, it's only common courtesy. At minimum. When we're dealing with the core of an application as popular as PHP, it's also an issue of responsibility. Zeev -- PHP Development Mailing List To unsubscribe, visit: http://www.php

Re: [PHP-DEV] Re: output buffering

Agreed, it's only common courtesy. david > > Zeev Suraski wrote: > > > The least you should do is > > > ask either Sascha or me how come it uses chunked buffering, and whether > > > it's not a bug. You would have gotten a pretty clear response saying > > > that it fully supports chunked bufferi

Re: [PHP-DEV] Re: output buffering

> Zeev Suraski wrote: > > The least you should do is > > ask either Sascha or me how come it uses chunked buffering, and whether > > it's not a bug. You would have gotten a pretty clear response saying > > that it fully supports chunked buffering. > > No. I don't think I need to ask. Sometimes y

Re: [PHP-DEV] Re: output buffering

At 14:51 07/10/2002, Yasuo Ohgaki wrote: >Zeev Suraski wrote: >>The least you should do is ask either Sascha or me how come it uses >>chunked buffering, and whether it's not a bug. You would have gotten a >>pretty clear response saying that it fully supports chunked buffering. > >No. I don't th

Re: [PHP-DEV] Re: output buffering

Zeev Suraski wrote: > The least you should do is > ask either Sascha or me how come it uses chunked buffering, and whether > it's not a bug. You would have gotten a pretty clear response saying > that it fully supports chunked buffering. No. I don't think I need to ask. It may be able to be c

[PHP-DEV] Re: output buffering

At 12:24 07/10/2002, Sascha Schumann wrote: > > A couple of questions for clarity: > > > > (a) Does this work properly with PHP 4.2? > > There is an even weirder bug, at least in the 4.2.3/CGI case > (the session output handler gets called after the request > shutdown which already di

[PHP-DEV] Re: output buffering

> A couple of questions for clarity: > > (a) Does this work properly with PHP 4.2? There is an even weirder bug, at least in the 4.2.3/CGI case (the session output handler gets called after the request shutdown which already disabled the session, so that the rewriter is not invok

[PHP-DEV] Re: output buffering

Sascha Schumann wrote: > The URL rewriter has been written to support handling of data > chunks, and thus your above statement "[the] URL rewriter may > fail to modify HTML correctly" is simply false. Just looked at the handler, the handler is storing intermediate result to global as

Re: [PHP-DEV] Re: output buffering

At 10:55 07/10/2002, Yasuo Ohgaki wrote: >As I said before, I don't touch any of chunk size related code. >You've removed all applicable lines regarding to implicit flush >thing. No implicit flush please. Enough. It's over. Seriously, please, it's really getting on my nerves already :) [*] >

[PHP-DEV] Re: output buffering

> Anyway, using unlimited size of buffer makes sense to me. > Unless it buffers whole contents, URL rewriter may fail to > modify HTML correctly. > > I don't read code, so I cannot make comment on this. Right, you did not read the URL rewriter code and so you should not comment on it.

[PHP-DEV] Re: output buffering

Zeev Suraski wrote: > 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 use

[PHP-DEV] 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 (an