Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of chip@force-elite.com
 designates 72.232.80.58 as permitted sender)
Message-ID: <491650E5.1010508@force-elite.com>
Date: Sat, 08 Nov 2008 20:54:29 -0600
From: Paul Querna <chip@force-elite.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: ApacheCon Presentations
References: <49150964.6030108@force-elite.com> <491589EF.6040806@sharp.fm>
In-Reply-To: <491589EF.6040806@sharp.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Graham Leggett wrote:
  > When you say "in the core", do you mean "in the /server directory in 
the
> source", or do you mean in "modules/wombat"?

modules/wombat initially.

> What does mod_wombat in the core buy us?

sanity.

> If I don't want mod_wombat, can I choose to not load the module like I 
> can choose to not load any of the others?

yes.

> How big is mod_wombat?

as big as it needs to be to bind the lua langauge to everything? (not 
sure the point of this specific question,  the weight of an individual 
lua VM is tiny compared to everything else in the universe.)

> I understand that the intention is for mod_wombat to be used in aiding 
> configuration, what if I just want to stick with a plain old flat 
> non-programmatic config file, will I still be able to do that?

yes.

I want it on by default though.

If you compile with --disable-wombat, sure, things will keep working for 
you like it did in 2.2, in the near term, but I want it to be defaulting 
to ON so we can actually change how people configure their servers, to 
you know, make it not suck.

-Paul