Apache 1.3.x vs. 2.0.x: The Debate Returns

darthcamaro writes "internetnews.com is running a story about the new Apache 2.0.49 release. They actually got a hold of a pair of Apache Software Foundation members and got them to speak out about the 1.3.x vs. 2.0.49 debate! Also Apache Director Sander Striker told internetnews.com that he expects the Apache 1.3.30 release cycle to begin this week... I still use 1.3.x because I've been using the Apache 1.x series 'forever' and I've never found a solid reason to change. Also, as pointed out in this article, the official PHP documentation clearly states, 'Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows.'"

Comments

Re:I run apache 2 and PHP in production

[justMichael]

And how many releases of each have we gone through since June 2002?

PHP was at 4.1.2, it is currently at 4.3.4

Apache was at 2.0.39, it is currently at 2.0.49

I have a feeling there have been some significant changes over the past (almost) 2 years.

If I had a spare box around here I would do some testing. I have been using Apache2 and PHP4 exclusively for over a year and have seen no problems.

I'll move to 2.0.x when...

[afabbro]

...mod_perl does ;) Seriously. I (like many others) love HTML::Mason. HTML::Mason doesn't work with mod_perl 1.9.x and masonhq isn't going to make it work with mod_perl 1.9.x because they don't want to invest the energy in a pre-production release. I can't blame them. Until mod_perl goes to 2.0, I'm not going to ;)