Re: usage of sapi dependency in PEAR packages

On 8 May 2004 at 18:46, Laurent Laville wrote: > > On 8 May 2004 at 18:02, Laurent Laville wrote: > > > > > Today on my way to completed tests under PHP 5.0.0RC2 > > > for my package HTML_Progress (version 1.2.0), i've discovered : > > > > > > 1. * HTML_Progress 1.2.0 is PHP 5 compatible (good new) > > > 2. * HTML_Progress (all versions) is not CGI server API compatible. > > > > Hi Laurent, > > > > what problems exactly exist there with CGI? You know I've tried out > > HTML_Progress several times in several browsers. And I was the CGI- > > sapi with a wrapper in Apache. > > > > Stefan > > > Hello Stefan, > > All my tests i've done was on a unique PC with both PHP 4 (4.3.6) and PHP 5 > (5.0.0RC2) > installed as CGI module. > I can't see any results until end of progress (reach 100%), then the bar is > displayed > > Probably we need to investigate more ; and if PEARs users could send us > their feedback it will be very cool :) Ah, okay. Now I know what you are after. Well, generally HTML_Progress works fine. But I agree with you about the output- buffering PHP/Apache do. I tried to solve it with flushing the PHP output-cache here, but I believe it has got something to do with a caching CGI-interface on the Apache-side. But maybe this is just a configuration-issue with Apache, and maybe on other CGI-executing environments (to use a general term) this problem also does not exist. So maybe adding a note in the docs but leaving the sapi- dependency away from the package.xml might be a solution? Stefan