Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 34250 invoked by uid 500); 26 Feb 2002 15:57:43 -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 34195 invoked from network); 26 Feb 2002 15:57:43 -0000 Reply-To: From: "Ryan Bloom" To: Subject: RE: cvs commit: httpd-2.0/server core.c Date: Tue, 26 Feb 2002 07:57:44 -0800 Organization: Covalent Technologies Message-ID: <002e01c1bede$5458d6d0$7f00000a@KOJ> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <3C7BB152.D4DE68F6@Golux.Com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Ryan Bloom wrote: > > > > I don't care how de-stabilized the code base becomes. > > That's a very alarming thing to read. > > Making perchild work is one thing. Warping, or even just tweaking, > common code in order to make perchild work is something else > again. If you read the statement in context, it shouldn't be alarming. It was in response to a statement that we shouldn't be re-writing any code, because it destabilizes the current code. I patently disagree with that statement. I also disagree that just tweaking common code should be a problem. Perhaps most importantly though, I don't think the changes for perchild will extend beyond the MPM. Ryan