On Wed, Apr 11, 2001 at 01:06:56PM +0300, Boian Bonev wrote:
> > > > Perhaps optionally disabled.. --without-cgi?
> > > I would go for optionally on, I really dont want to build both the
> apache
> > > module (p.e.) AND the CGi at the same time. For QA testing this is fine,
> > > but not for production servers.
> >
> > If you want to use the PEAR tools, you need the CGI version. These
> > are definitely intended for production servers.
> >
>
> i'd also preffer to have both versions - on all of my production servers i
> do install both apache module and cgi version. the latter i use for cron
> jobs, background processing and whatsoever tasks that need to do something
> outside the web. so in my opinion both sapi module and cgi will be a fine
> default. one more 'little' binary in /usr/local/bin would harm noone. also
> some isp configurations with several sapi setups on the same machine would
> benefit easier maintenance with this option. of course a way to disable it
> is ok but since PEAR needs the cgi ver to be able to fetch modules and etc
> the default should be 'enabled'.
Also it make sense to separate all but SAPI modules into shared library
to which SAPI module is linked dynamically. Then SAPI module binaries will
all share one code.
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | ALT Linux Team | Minsk Linux Users Group
www.midgard-project.org | www.altlinux.ru | www.minsk-lug.net
-- You won't skid if you stay in a rut.
-- Frank Hubbard
--
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]
