From: "Brian Behlendorf" <[EMAIL PROTECTED]>
Sent: Tuesday, June 12, 2001 10:01 PM
> On Tue, 12 Jun 2001, William A. Rowe, Jr. wrote:
> > Trick question, let me explain...
>
> I think people like him are asking: when is the fiddling done, and people
> have a program they can start to incorporate into their operating system
> releases, deploy for production customers, etc? While we're still working
> on low-level issues like pools/sms in APR and fixing other big performance
> issues, we're not there yet.
Agreed, but let's not be too obsessed about performance vs. architecture.
If the architecture is right, optimization becomes trivial in 2.0.21, .22, etc,
so sms-enhanced pools are a precursor to a release. Full implementation of
twelve alternate memory allocation structures is not.
I see very few showstoppers remaining to a general 'find the bugs' beta release
in the course of the next two weeks. Resolving the query-scoreboard and getting
the lifetimes straightened out first is key (and sms helps with alternate
lifetimes.) But I don't see any more "Big Things" to hold up 2.0. We are close
enough to taste it.
To have mod_ssl/tls all wrapped up for the general release would be fantastic,
of course, but it would be nice to know Apache 2.0 sans ssl is as solid and
far superior to Apache 1.3 even before that's introduced.
If it means that we end up with a stable release in July, without the mod_ssl,
that's fine by me. If the next stable 2.0 incarnation rolls in mod_ssl, I think
everyone could live with that. If proxy reaches stability when Apache does, then
great, call them both stable. Otherwise, we have Apache 2.0 stable, including
proxy beta candidate. The parts ought to grow and stabilize on their own.
The async and layered I/O ideas are great, and both would take some time (6 mos?)
to evolve. But somewhere along the line we have to decide 'that's 2.1.'
> I think it's enough to state "as soon as the showstoppers are out of
> the httpd-2.0/STATUS file" as a qualifier for that. Hopefully it means
> folks are focusing on those issues.
One hopes :-) Can't forget though that it's one's own itches. Apache tries to prove
that many coders, pulling the oars to their own sense of rhythm, create something
worthwhile. Some days the oars get tangled, but I think we succeed neverless.
