httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: [PATCH] XHTML/CSS support in mod_autoindex
Date Fri, 08 Feb 2002 16:27:45 GMT
From: "Greg Ames" <>
Sent: Friday, February 08, 2002 9:20 AM

> yet more evidence that we _really_ need to get a stable Apache 2.0 (as in,
> beta/GA with usable binaries) into widespread use.

No doubt.  I cleaned up 2.0 for XML syntax some great time ago...

almost considered a backport, but nahhh... 2.0 will be out soon!
Or so I believed.

> Otherwise we're going to see more and more pressure for new features in 1.3 
> which will eat into our available time.  

The only developers pressured are those terribly interested in the 1.3 code.
I was the only one hacking on Win32 for some time, because others were sure
that 2.0 was just around the corner, but I saw a broken build model.  Once
apxs worked on 1.3, I new I had succeeded.  Now I feel little pressure, except
from the XP send() corruption bug [in XP but there must be a workaround!]

New features :-?  Ha.  If contributors are busy 'improving' [read, introducing
new opportunities for brokenness in] 1.3, then they either have too much time 
on their hands, insufficient confidence in 2.0 or want to see 1.3 remain a
strong viable solution for the near or long term.  When you look at how long 
it took for the world to adopt 1.3 from 1.2, and the fact that development is 
a matter of scratching our individual itches, then it's not a huge issue.

> I am discouraged by the amount of churn in the 2.0 code base with negligible 
> benefit to users.

But massive benefits to module authors.  Apache HTTP is as strong as it is,
and gets so much devoted attention with corporate blessing precisely because 
it is an incredible platform to extend.

Unfortuantely, some bits like input filtering were 'left unfinished' when the
filtering changes went in.  That means we've experienced some pains with that
part of the 2.0 model.  I believe Justin's overhaul substantially corrects
those design deficiencies.  It's not perfect, perhaps, but getting as close
as 2.0 will ever come.  The change was painful, but necessary.


View raw message