Check out my Linux Magazine article from January, which was just posted online recently.</shameless plug>
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
./configure --help
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.
I'm pretty sure the answer is still "yes." Though I believe there's a hotfix from MS available for XP that fixes the problem. Have a look at this page, which explains the issue: http://www.apache.org/dist/httpd/binaries/win32/#x pbug and points you at the corresponding MSKB article.
Apache will never run as fast as iPlanet or Zeus because it is more sophisticated. It's definitely better than Apache 1.3 as of late, though. Look through the archives for dev@httpd.apache.org and search for a message from Brian Pane a week or two ago when we were putting the finishing touches on the bucket brigades API work... he posted some performance comparisons there.
As for iPlanet and Zeus... maybe in Apache 2.1 or 3.0 or whenever we get the async I/O MPM that we've been talking about, then we'll come closer. But still, you just have to expect that it's a tradeoff: do you want ultra-fast performance on a fairly simple web server, or do you want really good performance on highly customizable web server?
LDAP support was moved to a subproject of httpd. You can checkout the httpd-ldap tree from anonymous CVS if you like. No guarantees on whether it works at the moment, as I haven't tried it. Guess I should do that sometime soon.;)
This should be fixed in HEAD for PHP already as I understand it. These compile errors are a result of the bucket brigades freelist API changes that went in to 2.0.34. I've heard there are some residual problems with PHP HEAD, but those are being debugged as we speak.
Slashdot Mirror
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.
I'm pretty sure the answer is still "yes." Though I believe there's a hotfix from MS available for XP that fixes the problem. Have a look at this page, which explains the issue: http://www.apache.org/dist/httpd/binaries/win32/#x pbug and points you at the corresponding MSKB article.
Apache will never run as fast as iPlanet or Zeus because it is more sophisticated. It's definitely better than Apache 1.3 as of late, though. Look through the archives for dev@httpd.apache.org and search for a message from Brian Pane a week or two ago when we were putting the finishing touches on the bucket brigades API work... he posted some performance comparisons there.
... maybe in Apache 2.1 or 3.0 or whenever we get the async I/O MPM that we've been talking about, then we'll come closer. But still, you just have to expect that it's a tradeoff: do you want ultra-fast performance on a fairly simple web server, or do you want really good performance on highly customizable web server?
As for iPlanet and Zeus
LDAP support was moved to a subproject of httpd. You can checkout the httpd-ldap tree from anonymous CVS if you like. No guarantees on whether it works at the moment, as I haven't tried it. Guess I should do that sometime soon. ;)
This should be fixed in HEAD for PHP already as I understand it. These compile errors are a result of the bucket brigades freelist API changes that went in to 2.0.34. I've heard there are some residual problems with PHP HEAD, but those are being debugged as we speak.
Yep, it works fine!