----- "Howard Chu" <hyc(a)symas.com> wrote:
This also brings me to another topic - adopting features from
expose a cn=Tasks tree which can be used for submitting tasks via
Currently we expose our runqueue under cn=Monitor but that's only
It would be nice to be able to submit/schedule/trigger tasks on the
particular, it would be nice to have a defined task for triggering a
That would be nicer that having to remove and then add a syncrepl statement.
The Android slapd config would be a refreshOnly syncrepl consumer.
also have a hidden back-ldap refreshOnly consumer replicating from its
database and writing to the remote master. This way both push and pull
be under control of the Android device. (You have no idea how much of
you can rack up with fully automatic background synching. It's much
have this under complete user control.) The GUI would just submit a
cn=Tasks to trigger a synch.
OpenDS also has matching rules defined for comparing timestamp
"current server time". This is extremely handy for a lot of things.
this is a small, self-contained project that should be simple for
jump in on.
More ideas later...
All very cool and very handy. I soo wish I could have made it. Any ideas of next years
venue? Europe (London ;-) )?
OpenLDAP Engineering Team.
Community developed LDAP software.