Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 6528 invoked from network); 24 Sep 2004 22:32:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 24 Sep 2004 22:32:44 -0000 Received: (qmail 83968 invoked by uid 500); 24 Sep 2004 22:34:53 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 83302 invoked by uid 500); 24 Sep 2004 22:34:48 -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 83289 invoked by uid 99); 24 Sep 2004 22:34:48 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [137.65.81.169] (HELO sinclair.provo.novell.com) (137.65.81.169) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 24 Sep 2004 15:34:46 -0700 Received: from INET-PRV-MTA by sinclair.provo.novell.com with Novell_GroupWise; Fri, 24 Sep 2004 16:34:45 -0600 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.3 Beta Date: Fri, 24 Sep 2004 16:34:32 -0600 From: "Brad Nicholes" To: Subject: Re: new config organization for 2.1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Maybe I am jumping in here out of turn, but let me ask the obvious question. Why would we want to split the standard base httpd.conf file up into multiple files? Doesn't this end up just confusing the average user? One thing that I always tell new users of Apache is that rather than trying to understand the entire alpabetical list of directives in the httpd docs, go read the comments in the standard httpd.conf file. This gives them a good idea of what the base set of directives are and how they are used in a working context. For newbies reading a single .conf file seems easier to understand than trying to trace through multiple .conf files just to figure out the big picture. For those that are Apache experts, they have already rewritten and rearchitected the the httpd.conf file to fit their needs so they don't care. I can understand splitting dead or rarely used directives out, but it seems much easier to read as a single file. Maybe just some additional formatting and comments to distinguish MPM directives from Language from Vhosts, etc. is needed. Brad Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com