Date: Fri, 10 Oct 1997 12:56:59 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: config reading/parsing
In-Reply-To: <Pine.NEB.3.96.971010154451.9228A-100000@localhost>
Message-ID: <Pine.LNX.3.95dg3.971010125537.15904A-100000@twinlark.arctic.org>
Return-Path: Dean Gaudet <dgaudet@arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: O
X-Status: 

Right.  Doug and I talked about this earlier in the summer, maybe july?
At the time we both thought it would be nice for a callback to be added...
I actually suggested a getline() callback.  You just stuff a void * and
callback into the cmd_params and make sure it gets passed around and used
right ... should only be a few lines of code.

-- 
Dean Gaudet, Performance Analyst, Transmeta Corp.

On Fri, 10 Oct 1997, Rob Hartill wrote:

> 
> I just ran into a brick wall with the config reading code. Say I
> have a section of config 
> 
> <Location />
> ExpiresActive on
> </Location>
> 
> Unless I've missed it, Apache insists that this info must come from
> a file or I have to jump through all sorts of hoops to call all the
> necessary functions to get the config acted upon. The problem is
> that all the config parsing code is hardcoded to use file reads to
> get additional config input.
> 
> What'd be better would be if I could register some function to be
> used to 'get_the_next_char'.
> 
> What I wanted to experiment with was dynamic creation of
> raw Apache config directives from mod_perl, which could be fed into
> Apache's config parsing code as a big string, and treated as if it
> came from a .conf file.
> 
> 
> --
> Rob Hartill                              Internet Movie Database (Ltd)
> http://www.moviedatabase.com/   .. a site for sore eyes.
> 
>