<[EMAIL PROTECTED]> said:
[...] > > But then we would need a set of config tools for those using LDAP, and > those not using LDAP (although it should really only be very small > installations not using LDAP). If instead, libconf could handle LDAP also, > a config tool would only need to support libconf, and would get LDAP (and > XML etc etc) for free. that's right. > > For synchronisation, care should be taken where development on the > original software is aiming at LDAP, to not have incompatible LDAP schemas > .... > >>> >>> For applications where configuration can be stored in LDAP (such as >>> Postfix canonical maps etc), the backend should be capable of >>> supporting this, but at present most systems capable of reading >>> configuration from LDAP still require a config file to tell them where >>> to find the LDAP server (among other things). This will change I >>> think, as the use of DNS to locate services becomes more popular (ie >>> Kerberos-style SRV records). >> >> if the backend is capable of that, no need to use libconf, because no >> synchronization is needed. >> > > So there are currently configuration frontends that are sufficient for all > LDAP use? > > Instead, if libconf can write to LDAP also, I don't know ldap enough it seems. I thought that using some ldap library would make it as easy to deal with ldap as it is with libconf. If it's not the case, then of course libconf can be used as ldap frontend. That mean that we'll need C/python port sooner than I thought. > >>> >>> > provides a mapping of these >>> > information into a convenient perl structure. It is planed to have >>> an xml output, and a ldap output. You would then be able to ask >>> libconf to write an xml file from a standard config file. Or to feed >>> a ldap base. >>> >>> I think the big thing is that the API for frontends needs to be >>> defined, as perl structeres aren't that portable (for instance, >>> consider a remote Windows front-end ...). >> >> sorry, I don't understand your point completely :/ > > At some stage, there may be applications that want to use libconf as a > backend which are not written in perl ... I didn't see any documentation o > this aspect ... no port is done for now :/ -- dams
