In a message dated 1/11/2004 12:12:18 AM Eastern Standard Time,
dvdmandt@telia.com writes:
.. There really should be another configure parameter which names all
non-language stuff php5 instead of php... Like x-httpd-php5, php5_gd2.dll
and so on..
I'm +1 for that, if it matters.
And that seems to be the only thing that's holding it back from working...
the PHP5 module automatically takes over the x-httpd-php type, while the CGI
version has to be specified and can be specified to only use x-httpd-php5 (which
is what it does now).
Gordon Hemsley
Migration from PHP 4 to PHP 5 should be quite easy. I don't think we should
get into trying to make them co-exist. We might hit quite a few bumps on
the way.
I think that until you are ready to completely migrate, running PHP 5 as a
CGI is a decent solution.
Andi
At 01:09 AM 1/11/2004 -0500, GPHemsley@aol.com wrote:
In a message dated 1/11/2004 12:12:18 AM Eastern Standard Time,
dvdmandt@telia.com writes:
.. There really should be another configure parameter which names all
non-language stuff php5 instead of php... Like x-httpd-php5, php5_gd2.dll
and so on..
I'm +1 for that, if it matters.And that seems to be the only thing that's holding it back from working...
the PHP5 module automatically takes over the x-httpd-php type, while the CGI
version has to be specified and can be specified to only use x-httpd-php5
(which
is what it does now).Gordon Hemsley
Symbol clashes and other weird stuff I can't think of right now. Versioning
doesn't always seem to do all of the tricks.
At 08:08 PM 1/11/2004 +0100, DvDmanDT wrote:
For me it's not really a problem, but that's in my case... Lots of ppl
obviously wants both of them... So.. If it's only about naming the parameter
might be worth to think about.. Also, what bumps do you expect to hit?--
// DvDmanDT
MSN: dvdmandt¤hotmail.com
Mail: dvdmandt¤telia.com
"Andi Gutmans" andi@zend.com skrev i meddelandet
news:5.1.0.14.2.20040111210347.01fd9930@127.0.0.1...Migration from PHP 4 to PHP 5 should be quite easy. I don't think we
should
get into trying to make them co-exist. We might hit quite a few bumps on
the way.
I think that until you are ready to completely migrate, running PHP 5 as a
CGI is a decent solution.Andi
At 01:09 AM 1/11/2004 -0500, GPHemsley@aol.com wrote:
In a message dated 1/11/2004 12:12:18 AM Eastern Standard Time,
dvdmandt@telia.com writes:
.. There really should be another configure parameter which names all
non-language stuff php5 instead of php... Like x-httpd-php5, php5_gd2.dll
and so on..
I'm +1 for that, if it matters.And that seems to be the only thing that's holding it back from
working...
the PHP5 module automatically takes over the x-httpd-php type, while the
CGI
version has to be specified and can be specified to only use x-httpd-php5
(which
is what it does now).Gordon Hemsley
Andi Gutmans wrote:
I think that until you are ready to completely migrate, running PHP 5 as
a CGI is a decent solution.
If you're running a webserver with dozens of virtual hosts and you want
to migrate them one by one it would have been nice to be able to
selectively choose PHP4 or PHP5 module for each virtual host. The CGI
solution is a poor crutch. But if you think it can't be done with
modules then we'll have to believe you I guess.
I think we need to spend more time on the migration process if there
ever is another major PHP version coming up. Not that I long for one, as
a user of the language I was quite happy with PHP4 :-)
- Chris