LDAP replication - sync LDAP database with local AB. This bug tracks only the server -> client copy - bug 17884 tracks a real sync, i.e. client -> server, i.e. updating the server with info enter in the local AB. It should be possible to leverage the ABsync code we have (originally written for AB <-> Netcenter sync).

ops

To describe this a bit more detailed: This bug is about copying entries from an LDAP server to the local address book. It would enable manual lookup of address data in the Mozilla address book application and autocompletion in the mail composer. The scalability would be limited to that of Mork, the database for the Mozilla address book, which lies somewhere over 1000 records IIRC. The LDAP sync should offer a filter/query, so the records copied are limited and specfic (e.g. if you are working for a multi-national corporation with 50.000 employees, you could copy only the records for your country).

Another way to approach this would be to implement an LDAP search UI, and then allow entries to be dragged (perhaps en masse) to the address book.

dmose, wouldn't that be bug 17879?

Ah, right you are.

Getting schizophrenic: Moving all bugs for Beonex <http://www.beonex.com> to my second Bugzilla identity <ben.bucksch@beonex.com>.

Giving away bug until I *know* that I will work on it.

bugs owned by nobody are unlikely to get fixed in 0.9.1. removing tm...

Oops, sorry, everybody, image attached to the wrong bug.

reassigning owner and adding ccs

per prd, marking nsbeta1. Target milestone needs to be updated.

reassigning to rdayal.

Please see the design document at : http://www.mozilla.org/mailnews/arch/LDAP_replication2.html The decision made is to implement the Change Log protocol. Implementation can be done by either modifying the existing nsabldapdirectory... classes or implementing new classes. Decision has been made to implement new classes for ldap replication to keep the code cleaner and easier to debug as well as for code re-usability in future for implementing LCUP or any other replication protocol.

Implementation will be done in two parts, replicating all entries on to a local addressbook Mork DB file (tracking bug # 128086) and replicating the changes since the last update implementing the change log protocol (tracking bug # 128087).

Adding myself. Should bug 128087 be a blocker for this bug?

Both the replication patches have been checked in; this bug is fixed.

Verified