Sites Rejecting Apache 2?

An anonymous reader writes "Vnunet reports on the low adoption of Apache 2 has caused its producers to advocate freezing development of the open-source Web server until makers of add-in software catch up. Almost six months after the launch of Apache 2, less than one percent of sites use it, due to a lack of suitable third-party modules." I'm not sure where they are getting the freezing Apache development part, more talk about forking for 2.1 right now on the httpd mailing list. The article does have it right though that until there is a reason to upgrade and the modules are in place that adoption is not going to happen. While the cores of both Perl and PHP are thread-safe, the third-party modules are not. This renders one the larger reasons to use Apache 2.0, the threaded http support, useless for applications using either of these application layers. It comes down to the question of whether the third-party module writers are better off supporting what is used or what is new.

Comments

Pre-Fork is Dead

[elphkotm]

One can only hope that eventually Apache 2.0 will be accepted and lead the way for real multi-threading of open source software. Pre-fork, although optimized in Linux (a poorly thought-out idea, IMHO), is a terrible and inefficient way to thread. Just kill it.

Re:I'm still waiting on PHP

[Beliskner]

As soon as they release a stable version for Apache 2 (aka 4.3.0), then I'll look seriously at switching. It's great that Apache 2 has stablized now, though, as it lets everyone else work around a stable project. We'll all get to Apache 2, it just takes time to migrate.

Bwa ha ha ha!!! You /. people are so hypocritical, when Microsoft iis users fail to install patches to upgrade immediately and get mod_Code Red automatically installed via Internet you say "l4amers", and yet when it's your turn to upgrade Apache, or even just to patch the older vulnerable version, it's suddenly OK to wait, if it ain't broke don't fix it. Yeah well maybe I've got MS iis running with mod_Code Red but if it ain't broke don't fix it, yeah?

Re:I'm still waiting on PHP

[Beliskner]

It can be worse to install a security patch - remember M$ SP6 being corrupt, requiring SP6a? Remember Media Player XP forcing DRM down our throats? I'd say these changes are bigger in the big picture than a simple httd change which can always be rolled back. Proof of everyone worldwide signing a DRM patch click-through clause is much bigger than this.