[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: commit: ldap/servers/slapd/back-monitor back-monitor.h database.c init.c proto-back-monitor.h

> -----Original Message-----
> From: Pierangelo Masarati [mailto:ando@sys-net.it]

> > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-monitor
> >
> > Modified Files:
> > 	back-monitor.h  1.31 -> 1.32
> > 	database.c  1.40 -> 1.41
> > 	init.c  1.70 -> 1.71
> > 	proto-back-monitor.h  1.16 -> 1.17
> >
> > Log Message:
> > Added readOnly attribute, can be toggled on individual databases.
> Howard,
> this change is very interesting since it opens many new scenarios even
> before back-config is available.

Yes... I'm thinking that back-config and back-monitor ought to look very
similar in certain areas, with the difference being that changes made to
back-monitor are runtime-only, and not written back to any config database,
while changes made to back-config will be saved as well as acting
immediately. This approach may be troublesome and/or confusing, not sure it's
the best idea just yet. (E.g., you can query back-config and see one thing,
but the server's true state is only reflected in back-monitor.)

There is plenty more thinking that needs to be done. I think keeping
back-monitor separate from back-config is desirable because it allows us to
distinguish temporary runtime changes from longterm config changes. But aside
from that, it is also desirable for them to be a single module; certainly
back-monitor will need to be updated whenever back-config receives an update.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support