On Fri, 6 Jun 2003, Les Mikesell wrote: > From: "Charlie Brady" <[EMAIL PROTECTED]> > > > > If you do that, you run into the "two bosses" problem. Has a record been > > deleted from LDAP, or added to the accounts DB by the manager, or > > vice-versa? > > Wouldn't the best way to eliminate this problem be to do away with the > e-smith text file database and use LDAP exclusively?
By itself, that wouldn't achieve a lot - parts of the flat file are already immediately mirrored in LDAP, and it wouldn't be difficult for someone to enhance the LDAP schema to include more information. I think a few people might have already done that, in fact. The more difficult design issues are determining whether a node is the master or a slave in a multi-server environment, and bootstrapping the required trust relationships. Then you need inter-node communication communication protocols so that configuration changes made on the master (i.e in LDAP) initiate configuration changes on the slaves. But if you wish to lose the flat file and use LDAP is the primary repository, then by all means go ahead. I, for one, will be ready to give it a spin when you are done. :-) -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Group Mitel Networks Corporation http://www.mitel.com/smallbusiness Phone: +1 (613) 592 5660 or 592 2122 Fax: +1 (613) 592 1175 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
