Hi,
I'm working on some issues with synchronous synchronization based on
SyncRepl.
I wanted to know what is the desired behavior. I see essentially two
scenarios:
A. All is handled with sync protocol
A.1: automatic complete sync phase (works fine)
A.2: automatic complete clean phase (not implemented)
A.3: handle SyncRepl event:
A.3a: handle add (OK)
A.3b: handle modify (not tested, but should be OK)
A.3c: handle delete (not implemented)
A.3d: handle present (?)
A.3 can be different depending on the LDAP server. e.g. for
SUN/Novell/OpenDJ there would be no present but there would be a modrdn.
For Active Directory I don't know which entries are sent by the server.
B. Handle only add/modify
B.1: automatic complete sync phase (works fine)
B.2: handle incoming entries (works fine but deleted entries, see #445)
In this case we must support deleting separately, by allowing to launch
LSC with -c option for a asyncLdapSourceService (see #35).
LSC code seems to be nearer of B, I can work to fix the last issues.
But I would like to be sure it is the desired behavior.
Regards,
Raphaël Ouazana.
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
