Re: RFE for future Apache integration
| From: | Wez Furlong | Date: | Sat, 17 Dec 2005 18:20:24 +0000 |
| Subject: | Re: RFE for future Apache integration | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21267@lists.php.net to get a copy of this message | ||
We await your patch to fix this.
--Wez.
On 12/16/05, Ron Korving <r.korving@xit.nl> wrote:
> I think it's very much worth fixing. More and more people use packaging
> systems (emerge, dpkg, ...) which don't allow for what you propose. Not
> everybody compiles their Apache and PHP themselves. It would be very
> userfriendly if something like the solution suggested by techtonik would be
> possible.
>
> - Ron
>
>
> "Jani Taskinen" <sniper@iki.fi> schreef in bericht
> news:Pine.LNX.4.61.0512161538020.22622@arfg.argcubovn.sv...
> >
> > To reliably run 2 PHP version, use separate apache instances.
> > And --enable-versioning itself breaks a lot of stuff.
> >
> > Short version: It's not worth it to try "fix" this.
> > Very short version: "Wont fix"
> >
> > --Jani
> >
> >
> > On Fri, 16 Dec 2005, techtonik wrote:
> >
> >>
> >> Hello, PHP.
> >>
> >> While it is not too late, cat I ask for one enhancement for PHP6
> >> integration with Apache2, which was omitten in PHP5 architecture.
> >>
> >> Use the same Apache server instance with PHP4 and PHP5 modules.
> >> It is ok to link modules with
> >>
> >> LoadModule php4_module "../php4/sapi/php4apache2.dll"
> >> LoadModule php5_module "../php5/php5apache2.dll"
> >>
> >> It is ok to add server type for them in different VirtualHosts
> >> <VirtualHost *:80>
> >> ....
> >> AddType php5-script .php
> >> </VirtualHost>
> >> <VirtualHost *:8080>
> >> ....
> >> AddType application/x-httpd-php .php
> >> </VirtualHost>
> >>
> >> Problem no.1:
> >> Even though php5-script works to make server call PHP5 handler instead
> >> of PHP4 error_log is full of srings like
> >> [Thu Dec 15 16:43:29 2005] [warn] Cannot get media type from
> >> 'php5-script'
> >>
> >> Problem no.2:
> >> It is impossible to specify php.ini for each module separately -
> >> PHPIniDir is used by both PHP5 and by PHP4 and you can't specify more
> >> than one PHPIniDir per configuration file. SetEnv PHPRC doesn't work
> >> in this case too.
> >>
> >> Problem no.3:
> >> It is impossible to specify exact php.ini file, which may not be
> >> called php.ini, but something like php4.ini or php_old.ini
> >>
> >> Problem no.4:
> >> Ability to change php.ini depending on user needs on shared hostings
> >> without new instance of Apache.
> >>
> >> I guess the solution to all the problems except 4 is not so hard, but
> >> for the future IMHO it worth to add it into your global tracker.
> >> Useful instrument while working on problem no.4 would be tool to parse
> >> and compare differences in configuration among users and group them
> >> accordingly.
> >>
> >> Thanks.
> >>
> >> --
> >> --t.
> >>
> >>
> >
> > --
> > Give me your money at @
> > <http://pecl.php.net/wishlist.php/sniper>
> > Donating money may make me happier and friendlier for a limited period!
> > Death to all 4 letter abbreviations starting with P!
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>