Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21245
Return-Path: <techtonik@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84106 invoked by uid 1010); 16 Dec 2005 11:30:44 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 84091 invoked from network); 16 Dec 2005 11:30:44 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Dec 2005 11:30:44 -0000
X-Host-Fingerprint: 64.233.184.200 wproxy.gmail.com Linux 2.4/2.6
Received: from ([64.233.184.200:50060] helo=wproxy.gmail.com)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 36/09-23096-365A2A34 for <internals@lists.php.net>; Fri, 16 Dec 2005 06:30:44 -0500
Received: by wproxy.gmail.com with SMTP id i4so851349wra
	for <internals@lists.php.net>; Fri, 16 Dec 2005 03:30:40 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=eGt1b4c0hck63d188QGh5jbj0v2cye6x8j22+orCdn3+ny9mamoy8UoYE9ZMv8H1+eAAB/R3EY/npXZOR+2bTMLw5t1vuKBNscSI34sGLYu89qsm/xpoTtWVlQ1FArroAB7ZcFHJF0Y0b76ufGkAltS8yNYBhUNaQFZNpAQbNTg=
Received: by 10.65.75.3 with SMTP id c3mr1380167qbl;
	Fri, 16 Dec 2005 03:30:40 -0800 (PST)
Received: by 10.65.105.2 with HTTP; Fri, 16 Dec 2005 03:30:40 -0800 (PST)
Message-ID: <d34314100512160330u627525e6qb966af19cfe9e8a2@mail.gmail.com>
Date: Fri, 16 Dec 2005 13:30:40 +0200
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: RFE for future Apache integration
From: techtonik@gmail.com (techtonik)

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.