// It is not a stable version and the internals are changing way too much
// and too fast :).
Comments like this won't give most Apache evangelists/patrons the warm
fuzzies... When you make claims as strong as this, please follow them up
with statements that assert credibility (eg. "Hello I'm Ryan Bloom") or
with suitable evidence supporting tehm.
I've been running a 2.0.20 in a production environment for more than 8
months and it hasn't crashed on me a single time. This server btw
satiates most of the cool new functional features of Apache.
Since the cvs version of mod_php was crashy, we were running
php4.0/apache1.3 through mod_cgid, and even that was running quite well.
Apache 2.0 has been in the making for almost 5 years now, and the developers
have been ironing out bugs and problems for the past couple of months. For
me, 2.0.20 - to my mind, the most stable beta in the 2.0 series would've
easily qualified for release (except that everything around it was incompatible).
// It probably needs redoing quite a bit of your Apache
// modules.
2.0 has a new, simplified modules API. Hence, all your modules need to be
rewritten. Unfortunately, I haven't worked with 1.3 much, so I won't be
able to enlist differences, but off hand...
* 2.0 features complete protocol independence. Most of the
HTTP specific code is now moved to mod_http -> http_protocol.c, which means
that Apache is now a general purpose platform to implement TCP based
protocols, not exclusively an http server.
* New MPM's (Multi Process Models) - 1.3 was less scalable and slower than
2.0 because it had only one MPM - the preforking model, which is the default
scheme followed on most Unices (i.e., fork on accept()).
The current one has the MPM's split up,
and configurable for different platforms, as well as different
requirements - eg. the worker MPM for heavy duty systems, winnt MPM for
Windows. This, to my mind is the most significant
feature in 2.0, and the one that has required the most effort. This means
that Apache2.0 on WinNT should give IIS and the likes a run for their money.
besides that, there's a whole new build system based on autoconf.
A pipe and filter based service architecture, just like in IIS. A whole
lot of new modules (mod_rewrite, mod_gz, mod_include...). A tighter, more
robust bucket passing and memory management mechanism.
Another important thing to observe is that only Apache-httpd has been
released so far. The APR, which is a separate project, and forms the basis
of most of the "internals" :) of the Apache platform has NOT been released
yet. This, to my mind means that (alas!) the release is still not complete.
APR has also been quite steady for quite some time, so the visible
specification is not likely to change hereafter.
Which is to say, that I wholeheartedly recommend it to everyone.
Sapan
================================================
To subscribe, send email to [EMAIL PROTECTED] with subscribe in subject header
To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header
Archives are available at http://www.mail-archive.com/ilugd%40wpaa.org
=================================================
