Re: fw: using the perl backend

Brett @Google wrote:

On Thu, Jan 28, 2010 at 5:31 AM, Dieter Kluenter <dieter@dkluenter.de mailto:dieter@dkluenter.de> wrote:

> The 2.4.x series seems to require a perl backend to require knowledge of
syncrepl, even if it's pushing
> to a perl backend on another server via a "standalone ldap proxy".

You don't need a perl-backend, just create a ldapclient with
Net::LDAP::Control::SyncRequest.
Unfortunately RefreshAndPersist doesn't do what ist should do, so only
RefreshOnly will work.

Hmm.. so how do you set the rid in this case ?

If the inial value of the cookie is "" when creating Net::LDAP::Control::SyncRequest then the server must create the actual cookie value?

Also if using this approach, i presume the server will need to create a contextCSN, how does the perl client tell the ldap server the rid to use in the contextCSN ?

I can't see any mention of anything like a rid parameter on the perl client side.

providers don't care about RIDs. They are solely a convenience mechanism used to give unique handles to each syncrepl config in a consumer.

CSNs do not contain RIDs.