[389-users] sub-tree synchronization/watching: persistent search questions
pspacek at redhat.com
Mon Jun 10 07:54:53 UTC 2013
thank you very much for your time.
On 7.6.2013 18:12, Rich Megginson wrote:
>>>>>> I can see another option:
>>>>>> To implement 389 plugin which will provide (very partial) support for RFC
>>>>>> 4533. The idea is to implement only state-less pieces (no cookies) and
>>>>>> return some error when client attempts to use a cookie.
>>>>> This would also likely use entryUSN for the cookie, internallly.
>>>> Yes, that was also my idea, but I don't want to implement the 'state-full
>>>> part' of the RFC in all it's complexity. Now I'm interested only in
>>>> detection that all existing entries were read :-)
>>> Sure, but it would be nice to implement the whole syncrepl protocol if you're
>>> going to have to implement it partially anyway.
>> I definitely agree, but unfortunately, I'm tasked with something different
>> and this syncRepl episode is only the small piece of the whole story :-)
> Sure, but this might be enough motivation for the core 389 team to pick and
> finish syncrepl based on what you started.
Okay, I created a ticket for RFC 4533 implementation:
More information about the 389-users