Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.243 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ei3GCMQXTHw3FCIMOJVoiAL990EdoBTT++pF/S6vvuvUjuusmsqJwT9C929zQd2M10jMFbYGuPzTkZs0aYrcinO8MQtTuwGhonjjsQh3bArkiU7jLfwWtyZhlJ52b4Ii75GRI57HvU+fETo5nbuI8ryiVYuTncVbphAuYFivSoM=
Message-ID: <d8269d910707120238k4f9e2d90y3f71cc19667f3d78@mail.gmail.com>
Date: Thu, 12 Jul 2007 11:38:44 +0200
To: ceo@l-i-e.com
Cc: jani.taskinen@iki.fi, 
	"PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <2067.24.1.37.132.1184199932.squirrel@www.l-i-e.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <d8269d910707111543t3d8ea2a1ga38f8857a6836618@mail.gmail.com>
	 <469562DD.2030601@sci.fi>
	 <d8269d910707111613s13b02919tbbfe097de4912d23@mail.gmail.com>
	 <2067.24.1.37.132.1184199932.squirrel@www.l-i-e.com>
Subject: Re: [PHP-DEV] Apache handler with Multiple PHP versions
From: tijnema@gmail.com (Tijnema)

Hello Richard,

On 7/12/07, Richard Lynch <ceo@l-i-e.com> wrote:
> On Wed, July 11, 2007 6:13 pm, Tijnema wrote:
> > On 7/12/07, Jani Taskinen <jani.taskinen@sci.fi> wrote:
> >> A lot easier (and works already) is to install PHP as CGI/FastCGI
> >> (one version or all of them, one can be module of course) and define
> >> the
> >> required PHP version by the file suffix..
> >>
> >> --Jani
> >
> > Hello Jani:
> >
> > I know this is possible, and I believe it is possible in Apache too
> > with some kind of hack?
> > But this still doesn't solve a lot of problems, but will generate a
> > lot more with portable code. Take a bulletin board for example, there
> > are a lot of files inside a board, and when you want to install that
> > on your host that has PHP5 for files with .php5, you need to rename a
> > hell lot of files to .php5, AND change code inside the .php5 files to
> > point to the renamed files.
>
> No, you add a <Directory> config in httpd.conf or add to .htaccess a
> line like
> <Files ~.php>
>  ForceType whatever/gets/you/to/php-5
> </Files>

1) Did you ever see a shared host that has multiple versions
configured like this?
2) This will end up to be confusing for the end user, as they will
need to create the .htaccess file (as most users don't have write
rights for httpd.conf)

>
> Other problems:
>
> Getting 2 PHP modules to co-exist without tromping on each others'
> symbols is, I think, the show-stopper...

Both modules are different files, and only one will be dynamically
loaded by dlopen(), that works fine right? or do I forget something?

>
> It was possible to have PHP3 and PHP4 both as modules, I think, but
> that was an anomoly?
That was nice :)
>
> You also would have to re-think what happens when a version is
> requested that isn't installed at all...
>
> You currently have it just run in the default version, I think, but is
> that really useful?  If the code really NEEDS PHP 5, and the server
> doesn't have 5, only 4, running the code that needs 5 is probably not
> the right action...

I did, I think it should generate an error message,
E_RECOVERABLE_ERROR maybe? And then the default PHP version should
just give the code a try, just like it does when it is installed on a
host that has the wrong PHP version installed.

Regards,

Tijnema