Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 77560 invoked by uid 500); 8 Feb 2002 16:29:02 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 77547 invoked from network); 8 Feb 2002 16:29:02 -0000 Message-ID: <00d701c1b0bd$8f719e20$94c0b0d0@v505> From: "William A. Rowe, Jr." To: References: <20020208093217.GY4024@obsess.com> <3C63ECAA.3A84A5BC@remulak.net> Subject: Re: [PATCH] XHTML/CSS support in mod_autoindex Date: Fri, 8 Feb 2002 10:27:45 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-OriginalArrivalTime: 08 Feb 2002 16:27:54.0498 (UTC) FILETIME=[8F719E20:01C1B0BD] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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. Bill