Re: [389-users] sub-tree synchronization/watching: persistent search questions

>>>>> 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.