----- "Howard Chu" <h...@symas.com> wrote: <snip> > > This also brings me to another topic - adopting features from > OpenDS... They > expose a cn=Tasks tree which can be used for submitting tasks via > LDAP. > Currently we expose our runqueue under cn=Monitor but that's only > read-only. > It would be nice to be able to submit/schedule/trigger tasks on the > fly... In > particular, it would be nice to have a defined task for triggering a > syncrepl > refresh.
That would be nicer that having to remove and then add a syncrepl statement. > The Android slapd config would be a refreshOnly syncrepl consumer. It > would > also have a hidden back-ldap refreshOnly consumer replicating from its > local > database and writing to the remote master. This way both push and pull > would > be under control of the Android device. (You have no idea how much of > a bill > you can rack up with fully automatic background synching. It's much > better to > have this under complete user control.) The GUI would just submit a > request to > cn=Tasks to trigger a synch. > > OpenDS also has matching rules defined for comparing timestamp > attributes to > "current server time". This is extremely handy for a lot of things. > Again, > this is a small, self-contained project that should be simple for > someone to > 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 ;-) )? -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghe...@openldap.org Community developed LDAP software. http://www.openldap.org/project/
