Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 22145 invoked by uid 6000); 29 Nov 1997 21:11:56 -0000 Received: (qmail 22139 invoked from network); 29 Nov 1997 21:11:55 -0000 Received: from saga20.stanford.edu (171.64.15.150) by taz.hyperreal.org with SMTP; 29 Nov 1997 21:11:55 -0000 Received: (from akosut@localhost) by saga20.Stanford.EDU (8.8.8/8.8.4) id NAA28873; Sat, 29 Nov 1997 13:11:48 -0800 (PST) Date: Sat, 29 Nov 1997 13:11:48 -0800 (PST) From: Alexei Kosut To: new-httpd@apache.org Subject: Re: .conf confusion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Fri, 28 Nov 1997, Dean Gaudet wrote: > The first is a statement of fact. The init() phase isn't called before > the config is parsed... in fact we're in need of a pre-config phase. But > that falls out of the API redesign I think -- the redesign where we > (mostly) ditch the module structure and go for one hook which is called > and the module must register itself for all the other phases. Agreed. FWIW, over winter break (another two weeks), I plan to sit down and write up a whole lot of words explaining exactly how I think the Apache 2.0 module API should work (except for configuration; configuration is someone else's problem). Hopefully that will spawn some discussion and maybe even some code ;) BTW, do the module names "apache" and "apachen" bother anyone else? Every time I check out a new Apache tree, I always end up with the wrong one. Methinks we should rename them "apache1.2" and "apache1.3". That way, there is no "apache" to get confused about, and we can make an "apache2.0" whenever we want to. -- Alexei Kosut Stanford University, Class of 2001 * Apache *