Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 50650 invoked by uid 500); 15 Apr 2000 18:24:32 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 50638 invoked from network); 15 Apr 2000 18:24:32 -0000 X-Authentication-Warning: dillinger.io.com: manojk set sender to manojk@io.com using -f Date: Sat, 15 Apr 2000 13:24:29 -0500 From: Manoj Kasichainula To: Apache Developers Subject: Re: I'm changing my mind about config modules Message-ID: <20000415132429.A9742@io.com> Mail-Followup-To: Apache Developers References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9-current-20000328i In-Reply-To: ; from gstein@lyra.org on Fri, Apr 14, 2000 at 12:11:00PM -0700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Fri, Apr 14, 2000 at 12:11:00PM -0700, Greg Stein wrote: > On Fri, 14 Apr 2000 rbb@covalent.net wrote: > > For the record, step two here is not trivial. It requires modifying how > > containers work, because currently containers actually read from the > > config file, and we don't want that in the new model. For that reason, I > > am not continuing with this work until the group reaches the conclsuion > > that I should, or until my other current project is done, which ever comes > > first. > > All the more reason to complete the work. By distributing the config > reading process in the current model, it prevents us from doing things > such as Manoj's simplified config syntax. Why? I don't see a problem with it.