[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: contextCSN
On Mon, Feb 16, 2009 at 3:11 PM, Howard Chu <hyc@symas.com> wrote:
> jakjr wrote:
>>
>> sessionlog is a log of changes in-memory. But refreshAndPersist should
>> replicate changes on fly.
>>
>> So, to me, don't make any sense to keep this two options together.
>
> Networks aren't perfect. If the consumer loses its connection and
> reconnects, the sessionlog will still help at that point.
OK, that is good reason.
So, after a network re-connection, the consumer should make a full
re-synchronization. Using Sessionlog prevents this, right ?
Thanks.
>>
>> Regards,
>> Jakjr
>>
>> On Mon, Feb 16, 2009 at 2:27 PM, Guillaume Arteta<arteta22000@gmail.com>
>> wrote:
>>>>
>>>> That bug is fixed in 2.4.14, you should upgrade.
>>>> --
>>>> -- Howard Chu
>>>> CTO, Symas Corp. http://www.symas.com
>>>> Director, Highland Sun http://highlandsun.com/hyc/
>>>> Chief Architect, OpenLDAP http://www.openldap.org/project/
>>>
>>> Ok.
>>>
>>> Small question :)
>>>
>>> Should we put syncprov-sessionlog in 1000 only with the mode refreshOnly?
>>> or
>>> also with refreshAndPersist (the one I use) ?
>>>
>>> Merci.
>>> -----------
>>> Guillaume.
>>>
>>>
>>
>
>
> --
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
>