You saw it in PHP 3/4.
And it can LOOK from the outside like you're doing it, using a
ProxyPass from one Apache box to another.But I'm pretty sure you can't get both versions into one build, as the
symbols collide big-time during the configure/make process...
Actually I read an article a couple of mos. ago where someone shared their
experience installing two versions on their box - 4 as the base (default)
install and 5 as the supplementary version. It was done as Apache modules.
The default was installed as any PHP version might be done, and 5 was
installed in the same $prefix but in the php5 directory - as opposed to the
php directory. This permitted the use of php version; by extension, per
directory, and/or by the use of .htaccess. Many others followed his article
and attempted to do it themselves. But reported failure. Turns out that the
one thing all failed attempts had in common was their OS (Linux). Linux
has a less efficient/flexible loading mechanism than *BSD(i). Which (as
you noted) causes symbol collision. The article was quite old, so I was
unable to get the beginnings of it. So perhaps Linux has since made some
provisions that overcome this problem (newer kernels). Anyway, I was hoping
that some with a similar (working) experience might share it here. As I'm
sure that ability would lend itself to generating an increased interest in
installing 5 (or 6) along with their base 4 install. It would also shorten
any attempt on my part to do the same. :)
Thanks for taking the time to respond.
P.S. Please don't top post. It buggers up the threads and breaks context.
On Mon, 9 Jul 2007 14:38:03 -0700, Andrei Zmievski
andrei@gravitonic.com wrote:Yes, backporting major features from PHP 6 to 5 will slow down PHP 6
adoption, and I'd like to avoid it if possible.There is a way to run two engines side by side, by the way: in
separate instances of Apache. It's really not that complicated.Isn't there some evidence of the ability to run two engines
side-by-side
with only one instance of Apache; thereby eliminating some overhead?
Wouldn't that actually be easier?
I could have sworn I saw that somewhere.-Andrei
IMHO backporting a lot of features to PHP4 is a major reasons for
the
slow PHP5 adoption. Basically, it seems that everybody who is not
using
OOP feels that PHP4 is fine for them.I'd say committing to backporting stuff from PHP6 to PHP5 will
yield a
similar situation: very slow or no PHP6 adoption.BTW, can't the unicode switch be done at compile time? So one can
compile PHP6 Unicode and PHP6 non-Unicode. Then if there is a
clever way
of running both engines in parallel, there should be no performance
impact inside the non-unicode engine. Since there is both versions
of
the engine (that can maybe even selected by a certain statement in
the
main PHP file of the application), unicode and non-unicode users
are
happy. And there is only one version of PHP in the market, to
conquer it
all.There must be a reason to upgrade to a new PHP version (usually
features, maybe performance increase etc.). But there also must be
no
reason not to upgrade. But you all know this, it has been said
before.Kind regards,
Stefan
--
e-novative> - We make IT work for you.
e-novative GmbH - HR: Amtsgericht München HRB 139407
Sitz: Wolfratshausen - GF: Dipl. Inform. Stefan Priebsch--
--
/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.--
--
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?
/////////////////////////////////////////////////////
Service provided by hitOmeter.NET internet messaging!
.