Slashdot Mirror
Apache HTTPD 2.0.28 Beta Released
This is a major
2.0 beta release
for the
Apache HTTPD Project.
The last publicly available beta was released in April (and the
ChangLog
is nearly 500k!). See what
the new features
are going into the 2.0 release. Please remember to
use a mirror.
this isnt newsworthy enough of the front page? WTF!? every time there's a minor version of mozilla released or minor release of a linux kernel it's front page news. but this a major release of apache - 2.0 beta. what - did the /. editors just think - nah no one's interested, just tuck it where no one will see it.
i know, i know, rtfm, but does apache 2.x still serve pages by forking a new process (i know, it preforks, blah blah, still you end up with dozens of processes)?
Yes, it does. There are a range of choices when you compile, but the threaded MPM is the default. There is also a Win32-specific multi-threaded engine.
until apache is a multithreaded server like AOLServer [aolserver.com] (don't laugh, it's open source and very, very good) or even a non-blocking IO server like thttpd [acme.com] it is just unusable for truly scalable or database-centric stuff
Well, it's not an issue now with Apache 2, but the above statement is simply not true. I can tell you that from experience running a scalable database-centric web application. The trick is to put a http accelerator / reverse proxy up front. It's easy to do and works very nicely.
Yes, it does. There are a range of choices when you compile, but the threaded MPM is the default. There is also a Win32-specific multi-threaded engine.
The one correction I'd like to make is that we disabled the threaded MPM by default after 2.0.16 was released. And, we've actually removed the threaded MPM *after* we released 2.0.28. The threaded MPM has been superceded by the "worker" MPM (our names aren't the greatest). The "worker" MPM is essentially threaded (but has multiple processes to increase redunancy) - you'll see us call this a MPMT (multi-process/multi-thread) MPM.
There is a discussion on-list about whether we should enable threading MPM by default if the OS supports it. It's an open question, but for now (and what is in 2.0.28), we use prefork by default. A configure-time option allows the selection of which MPM it should compile with.
FWIW, special platforms (like Win32) have their own MPM that is specific to their OS. The "worker" MPM is targeted towards UNIX-like platforms (Linux, Solaris, etc.).
Mu. P.S. The address you see is real. =)
I'd already modularized my pages as far as 1.3 would allow without using mod-perl but I had a few perl "utilities" that I couldn't get to work with my standard INCLUDEd navbar, header or footer scripts.
With 2.0, I can. In fact, I just did.
GTRacer
- Apache and Gimp on Win32...What's wrong with me?
Defending IP by destroying access to it? That makes sense, RIAA/MPAA. Go to the corner until you can play nice!