Erik van Oosten wrote:
Howard,
Thanks for your support and the quick fix!
You're welcome. And please post back here with more status on your syncrepl
implementation, I believe you're one of the first outside the OpenLDAP Project.
Regards,
Erik.
PS. I filled a second, much smaller,
Howard,
Thanks for your support and the quick fix!
Regards,
Erik.
PS. I filled a second, much smaller, syncrepl bug under ITS#5211.
Howard Chu wrote:
Erik van Oosten wrote:
Shall I report this as a bug?
Please do, thanks.
--
Erik van Oosten
http://2008.rubyenrails.nl/
Howard Chu wrote:
And please post back here with more status on your syncrepl
implementation, I believe you're one of the first outside the OpenLDAP
Project.
I am about done and quite happy with the result. I only need to write
code to restart aborted syncs and some more code to manage many
Erik van Oosten wrote:
There appears to be a detail missing from the RFC - when no changes
have occurred since the last refresh, for refreshOnly the provider
will send a Sync Done refreshDeletes control with no cookie. I.e., if
the state hasn't changed, the cookie would be identical, so there's
Thanks Howard,
Your use of the words client and server seem inconsistent here. The
above questions made no sense to me. Servers don't send polls.
Sorry, my interpretation of RFC4533 terminology :) . What I read is that
the client may select from 2 modes of operation (by providing an initial
Erik van Oosten wrote:
Still, this interpretation can not be correct. When I run my sync client
program against OpenLDAP (2.3.36), and then restart it after the refresh
stage with the last received cookie (note: the DIT remains unchanged), the
first message is exactly that SyncInfoMessage of
Hello,
I am writing a RFC4533 client implementation based on JLDAP. I have a
question on how to interpret the rfc as a client, and secondly how the
OpenLDAP server interprets it.
My question is: how can the client determine that it must delete content
at the end of the refresh stage, when a
Erik van Oosten wrote:
Hello,
I am writing a RFC4533 client implementation based on JLDAP. I have a
question on how to interpret the rfc as a client, and secondly how the
OpenLDAP server interprets it.
My question is: how can the client determine that it must delete content
at the end of the
