[Date Prev][Date Next]
Re: fw: using the perl backend
Brett @Google wrote:
> On Thu, Jan 28, 2010 at 5:31 AM, Dieter Kluenter <email@example.com
> <mailto:firstname.lastname@example.org>> 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
> 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
> 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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/