Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Subject: Re: 3.0 - Proposed Goals
From: Joachim Zobel <jzobel@heute-morgen.de>
Reply-To: jzobel@heute-morgen.de
To: dev@httpd.apache.org
In-Reply-To: <45D2BB47.10507@force-elite.com>
References: <45D2BB47.10507@force-elite.com>
Content-Type: text/plain
Organization: Not organized
Date: Thu, 15 Feb 2007 20:44:38 +0100
Message-Id: <1171568678.4332.12.camel@test.asus>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Am Dienstag, den 13.02.2007, 23:33 -0800 schrieb Paul Querna:
> - Build a cleaner configuration system, enabling runtime
> reconfiguration. Today's system basically requires a complete restart of
> everything to change configurations.  I would like to move to an
> internal DOM like representation of the configuration, but preserve the
> current file format as the 'default'. (Modules could easily write an XML
> config file format, or pull from LDAP).

A configuration command line similiar to a databases command line
interface would be nice to have.

The good thing with an XML configuration would be, that you could
validate it against a schema. Especially certain settings could be
unique. This would put an end to wondering why a conf. change has no
effect for an hour until discovering that the same value is set again
somewhere else in the config.

An XML command line however ... :)

Sincerely,
Joachim