Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Wed, 10 Jun 2009 10:17:00 -0400
Subject: Re: Some ramblings on httpd config
From: "Akins, Brian" <Brian.Akins@turner.com>
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Message-ID: <C655389C.C0855%Brian.Akins@turner.com>
Thread-Topic: Some ramblings on httpd config
Thread-Index: AcnpyoFXZyrSV6EZRfKR5MhUw8UYgAAC50dp
In-Reply-To: <8DE3F7C6-04CA-46BB-83C4-4DDFA6E35BB3@rcbowen.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 6/10/09 8:52 AM, "Rich Bowen" <rbowen@rcbowen.com> wrote:

> Or something like that that's sufficiently like what we have now to be easy to
> learn, but sufficiently different to be harder to get wrong, and a whole heck
> of a lot easier to do dynamic vhosts.

I think Lua (or whatever) could include enough "user friendly glue" to make
something like that possible.


> If we had a standard set of variables (like, say, HOSTNAME or whatever) that
> could be interpolated into config directives, as well as a standard way to do
> variable assignment and backreferences, that would solve a whole class of
> problems that are really pretty difficult right now.

That sounds a whole lot like using the config as a runtime.  Hmmm, where
have I heard that before ;)


-- 
Brian Akins
Chief Operations Engineer
Turner Digital Media Technologies