On Thu, Jan 03, 2002 at 09:37:38PM +0000, [EMAIL PROTECTED] wrote: > > It should still be possible to build a separate CGI executable with a > > different php.ini path for those sites that require it. > > Don't get too stuck on the idea that PHP at the command line is only > for CGI. In fact I don't do CGI any more. I am phasing out ALL perl > CGI scripts because after seeing PHP as a module I can't stand the > extra time it takes to execute the external program. PHP CGI has the > same problem. I just say NO to all CGI. Okay, this is kind of getting out of hand.
I don't really disagree with any of your points. All I was saying is that a normal build of PHP (say, for the Apache SAPI interface) should also include a CGI build, for command line usage. This CGI binary will be necessary for the PEAR tools. The fact that it might not be optimized for the user's command line scripting needs is irrelevant because they can go ahead and build their own custom CGI binary by executing 'configure' a second time. In other words, I'm talking about extending the default build to include a default CGI binary build. -- Jon Parise ([EMAIL PROTECTED]) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
