[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: backend requirements for syncrepl

To: "Pierangelo Masarati" <ando@sys-net.it>, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: backend requirements for syncrepl
From: "Jong-Hyuk" <jongchoi@OpenLDAP.org>
Date: Mon, 4 Oct 2004 12:10:57 -0400
Cc: <openldap-devel@OpenLDAP.org>
References: <415ED0C0.9060909@sys-net.it> <6.1.2.0.0.20041002093647.041a0170@127.0.0.1> <41604CF3.2090703@sys-net.it>

> >For CSN, you can construct something from any timestamp.
> >
> this should not be an issue.

Currently, a new entryCSN value is obtained and sent when entry is returned
by back-sql. Although it can be constructed dynamically from any timestamp,
the entryCSN for an entry should be derived from a static timestamp in the
database. Otherwise, synchronization session will always perform a full
reload.
- Jong-Hyuk

Follow-Ups:
- Re: backend requirements for syncrepl
  - From: "Pierangelo Masarati" <ando@sys-net.it>

References:
- backend requirements for syncrepl
  - From: Pierangelo Masarati <ando@sys-net.it>
- Re: backend requirements for syncrepl
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: backend requirements for syncrepl
  - From: Pierangelo Masarati <ando@sys-net.it>

Prev by Date: Re: backend requirements for syncrepl
Next by Date: Re: backend requirements for syncrepl
Index(es):
- Chronological
- Thread