- 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
Pros
Cons
Lack of documentation
Test suite with 2
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
-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 completely understand,
parse and manipulate Apache
I missed the Apache-Admin-Config module in my search for Apache config
file parsers, otherwise I would have not written a new one :) The
other parser was just announced after I finished this one is named
Apache::ConfigFile.
All three modules appear to treat the directives and contexts the
same,
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
