directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ersin ER <ersin...@gmail.com>
Subject Re: Toward 2.0...
Date Wed, 18 Mar 2009 10:18:44 GMT
I think this whole configuration stuff should go into its own thread.
"Towards 2.0" is more general view thread.

On Wed, Mar 18, 2009 at 11:06, Jeff MAURY <jeffmaury@gmail.com> wrote:

> If I correctly understood the need from the ADS point of view (and not from
> a pure technology point of view Spring vs ....), what the ADS team is
> looking for is a solution for configuring through an XML file with a simple
> syntax a set of classes and assembling them in a simple way (JavaBeans
> convention, no AOP, no IOC).
> So why not use commons digester (http://commons.apache.org/digester/) ? It
> is being used by Tomcat for a long time ago now and seems to fill the
> requirements ?
>
> Regards
> Jeff MAURY
>
>
> On Wed, Mar 18, 2009 at 2:20 AM, Howard Chu <hyc@symas.com> wrote:
>
>> David Boreham wrote:
>>
>>> Graham Leggett wrote:
>>>
>>>> That said, both Fedora and OpenLDAP use the DIT for config, so that
>>>> may be an XML free option :)
>>>>
>>> FDS doesn't exactly use the DIT. We had the same argument that you're
>>> having, in 1997 or so, and
>>> decided to write an 'ldif back end' for the server, specifically for
>>> config (there had been an earlier
>>> flat-file back end that provided some inspiration and possibly some
>>> code).
>>>
>>
>> Heh. Sounds like the same discussion we had in 2000, it took us a while to
>> get out of the weeds of LDAPv3 before we could see it. ;)
>>
>>  This replaced the original
>>> UMich text config file (which I believe OpenLDAP still used until
>>> recently). So while the config
>>> manifests as LDAP entries, and can be read/written over-the-wire, it is
>>> stored in a text file as LDIF.
>>> If it were in the primary database, you'd have a chicken/egg problem.
>>>
>>
>> Right. We wound up with an LDIF backend as well; it can still be
>> configured as a primary database (but that would be stupid) but its main
>> point is that it is so simple to configure (just needs a directory path to
>> store its files) that its bootstrap can be hardcoded, thus giving us the
>> initial egg.
>>
>> I also experimented with using back-ldap as the cn=config backing store;
>> i.e., running a server with a configuration proxied from (and thus identical
>> to) a separate server. But it's more reliable to just replicate the master's
>> config to a local LDIF copy. There's no reason we couldn't provide hardcoded
>> parameters for any other backend type as well, but back-ldif has the virtue
>> of being human-readable/editable in case Something Went Wrong...
>>
>> --
>>  -- Howard Chu
>>  CTO, Symas Corp.           http://www.symas.com
>>  Director, Highland Sun     http://highlandsun.com/hyc/
>>  Chief Architect, OpenLDAP  http://www.openldap.org/project/
>>
>
>
>
> --
> La mélancolie c’est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n’est pas capitaliste
> C’est même gratuit pour les perdants
> La mélancolie c’est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c’est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
>



-- 
Ersin ER
http://www.ersiner.net

Mime
View raw message