Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.78.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=lyRgiak72P+xHsQ+Ayu4q/euk0dSjESEMGyfl7Up89yT6HKHnnXoLJMcK6cP/Ckqrp
         FPatisJTPxJTDkwvmgufGeT0sUEu/NWknE+kOnBS0LPwplyz0c2mv/bMumVn9fSY/X4m
         zESTDeDt0Vpgh+ulLT6Ksf8lrqNNqDO4dB+C4=
Sender: Emmanuel Lecharny <elecharny@gmail.com>
Message-ID: <49C14DF7.9010406@nextury.com>
Date: Wed, 18 Mar 2009 20:39:35 +0100
From: Emmanuel Lecharny <elecharny@apache.org>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: ApacheDS ConfigNG
References: <a1b4a6610903181041i44331978r5011871900f44f75@mail.gmail.com>
	 <49C13760.8040709@nextury.com>
	 <A966E9AE-3BF0-4CF3-9FCB-54903DDB932F@yahoo.com>
	 <49C149EF.70201@nextury.com>
 <a1b4a6610903181227m2cd28c3coafb1296c378a8285@mail.gmail.com>
In-Reply-To: <a1b4a6610903181227m2cd28c3coafb1296c378a8285@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Ersin ER wrote:
> One of the things we should consider for a configuration mechanism is that
> whether this configuration format is for humans or is for tools. If it's for
> humans neither XML nor LDIF are good candidates. If it's for tools, both are
> fine and then there can be other criteria to select one or also both can be
> supported. I don't think one if superior to other in terms of
> expressiveness.
>   
I think that it does not matter too much. Or, more generally, a 
configuration mechanism should be versatile. From a human being, a GUI 
is obviously the best. But that mean we need a tool to read the 
configuration and to present it. Some prefer a text file (either because 
it's lightweight, or because you don't have a graphic terminal available 
), and then it should be straightforward. Of course, comments must be 
present.

So what we need is a Configuration bean, loaded from a configuration 
file, whatever the format of this file is.

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org