- Original Message -
From: "Blair Zajac" <[EMAIL PROTECTED]>
To: "Geoffrey Young" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, September 13, 2001 1:52 AM
Subject: Re: Pre-announce Apache::ConfigParser
> Apache::Admin::Config
>
Hi!
> I swore there was yet a third candidate in this realm, but I didn't see it
> on brief inspection.
I am currently sort of working (haven't touched for some time) on
something called Apache::FakeEnv which should be something like a subclass of
Apache::FakeRequest, but which includes access to
> I swore there was yet a third candidate in this realm, but I
> didn't see it on brief inspection.
Config::General also parses Apache-style config files, but I don't think it
handles Apache specific details like contexts.
Michael
I'll let the other module authors answer your API questions - I was merely
starting the dialogue :)
>Is it possible to remove CPAN modules when a common interface is built?
yes, PAUSE has a delete interface, which removes them from the various CPAN
mirrors. there is also an archive project goi
t possible to remove CPAN modules when a common interface is built?
Blair
Geoffrey Young wrote:
>
>
>
> >-Original Message-
> >From: Blair Zajac
> >To: [EMAIL PROTECTED]
> >Sent: 9/12/01 5:41 PM
> >Subject: Pre-announce Apache::ConfigParser
>
>-Original Message-
>From: Blair Zajac
>To: [EMAIL PROTECTED]
>Sent: 9/12/01 5:41 PM
>Subject: Pre-announce Apache::ConfigParser
>
>Hello,
>
>This is a preannounce of Apache::ConfigParser. I wrote this to
>allow programs separate from Apache to com
Hello,
This is a preannounce of Apache::ConfigParser. I wrote this to
allow programs separate from Apache to completely understand,
parse and manipulate Apache configuration files.
The interface is not simple, but it allows for more complicated
understanding of log files, such as finding the as