[Date Prev][Date Next]
Re: backend requirements for syncrepl
The requirements for the syncrepl consumer is different from that for the
provider. For syncrepl consumer, it should be assumed that only the syncrepl
engine updates the database, hence the mechanisms such as trigger and
TIMESTAMP would not be required. The syncrepl engine can then manage
entryCSN in ldap_entries. Perhaps I missed something during this thread
since I was not inline with the ldapsync control issue.
In my (preliminary) design, back-sql should act as a "dumb" syncrepl
producer, i.e. a producer that is barely aware of the syncrepl control
but can only answer in refreshOnly mode and simply responds to
I am currently into
the design of a changelog-based operatoin mode of syncrepl. Wondering
whether this would be sufficient for your case.
mmmh, that's again the producer's side, I guess, so the point is that
I don't see any reliable and generally portable way to know if the
producer's data changed, I'm afraid.
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497