Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id UAA11216; Mon, 15 May 1995 20:57:51 -0700 Received: from eat.organic.com by taz.hyperreal.com (8.6.10/8.6.5) with ESMTP id UAA11210; Mon, 15 May 1995 20:57:49 -0700 Received: (from brian@localhost) by eat.organic.com (8.6.11/8.6.9) id UAA10113; Mon, 15 May 1995 20:57:58 -0700 Date: Mon, 15 May 1995 20:57:57 -0700 (PDT) From: Brian Behlendorf Subject: Re: 0.6.4 looks fine here... To: new-httpd@hyperreal.com In-Reply-To: <9505160001.AA06830@volterra> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 15 May 1995, Robert S. Thau wrote: > A few comments as I come back in from the cold. First off, Apache > 0.6.4 looks fine here. We should probably release it; it may even > make sense to call it 1.0. At least 0.7, if it has the non-forking code. > As regards the non-forking stuff, I tried to run it a while ago, and > ran into real trouble with leaking file descriptors. The reason that > this wasn't a problem for anyone during 1.4 beta tests until quite > late was because of frequent process rotation, and while we may want > to adopt a more systematic approach (;-), it's the *easiest* > short-term cure. Long term, the best thing to do is probably trying > to fix them all (we can probably get a lot of the fixes out of the > diffs between middle 1.4 betas and 1.4 final). I suppose we can bundle it in (did it make it into 0.6.4, robh?) with the warning that it leaks, and that we're relying on the net at large to help us find the holes... have it kill its children only when they get really big so that people are motivated. :) > However, I am starting to feel the same about Cliff about whether we > can flog this pony another mile. It may be worth asking, at this > point, what sort of a server we'd really like to have, if we could > have the time to create it --- if we can keep the wishlist in check, > some sort of useful cleanups may be possible. If Apache is about 80% of the what we want feature-wise, maybe we should just commit ourselves at this point to bug fixing and the like, and look for a new core - be it MDMA (Simon?), WN, or something else. I'd like to think we could pluck out our favorite pieces of the code - the config file parsing (though I'd like to revamp the config file format, frankly) the content negotiation, etc - and put that on top of this new core. It might behoove all of us to start reading up on Java too :) Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/