Apache 2.0 Goes Gold!
The Apache Software Foundation's Apache
HTTP Server, version 2.0.35, has now been released for General Availability. You can find the official announcement, and download the server, from their website. Be sure to try a mirror first. Congratulations to the HTTP Server Project for getting the final release out. If you are wondering about it being usable in a production environment, you should poke around Slashdot's servers and see if you are surprised (now if only mod_perl was finished we could move more of our servers over to using the new release).
The HTTP Server Project is now recommending this release for use on production websites. 2.0.35 is now considered their best release and should be used in preference to all older versions (including the 1.3 series). A few of the new features are:
- higher performance over 1.3
- multiple operational models: threaded, hybrid multi-processes and multi-threaded
- specific request processing for Windows, Netware, BeOS, and OS/2
- integrated SSL and WebDAV support
- improved HTTP proxy support
- I/O layering and filtering
Upgrades are a little early unless PHP starts compiling in, especially statically. (A la mod_php without DSO). They're getting close, php 4.2.0 should work I suspect, whenever it or any other previewish release comes out.
Also, be nice to get some good benchmark numbers. Speed / SSL / Dynamic Content seem to be things just about everyone relies on, and it'd be great to have a nice case to move from 1.3. I know the Apache team has made a lot of progress on this, be great to see it validated.
Bravo all around of course.
- August
a while ago.
I can remember krow (aka Brian Aker) tell me in IRC about how he setup apache2 to just server images. Like the most simple thing you can do. It requires no special threading, or proces modes, just http1.1. At most, they can do geographic ad targeting with revers DNS lookups tied to the image servers. Blah... still not that special, but at least they can say they run apache2. I have also read where he claims apache2 is't ready for prime time. This is very telling, not because he is senior Slashdot developer, but more because he is known best for his apache 1.3 modules, such as mod_mp3, or mod_layout.
It isn't a lie if you belive it.
The short answer to your question: while yes, you can probably get your 1.3 config to work without *too* many changes, you should spend a bit more time exploring Apache 2.0, or you'll miss out on a lot of the benefits.
The configuration is totally different; it uses GNU autoconf now instead of the home-grown APACI system. The two have many similarities, but you should peruse all of the
options carefully.The perchild MPM (which provides the configurable userid per Apache child process that you mention) is possibly not yet working; it's still classified as experimental. But we'll probably be getting that cleaned up within another release or two.
For installation, I found that the easiest thing to do is to add
Somewhere in the document and, for indexes,
before the DirectoryIndex (which must be modified to add index.php). The CVS version works also, but I had problems with some scripts under it. Hope this helps. SiMac450
I haven't used the Kiwi File System though.
Bleh!