> > 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.
indeed this is only one more step in the build process - make the core php
lib then link to all the sapi modules on the configure command line and
install them one by one. you did not mean dll/so right? because the base
library must be a static one and then the sapi modules themselves may be
either dynamic or static...
b.
--
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]
