On Wed, July 11, 2007 6:13 pm, Tijnema wrote: > On 7/12/07, Jani Taskinen <[EMAIL PROTECTED]> 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> Other problems: Getting 2 PHP modules to co-exist without tromping on each others' symbols is, I think, the show-stopper... It was possible to have PHP3 and PHP4 both as modules, I think, but that was an anomoly? 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... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
