Re: what if we move SLAPI to a (global) overlay?

["Pierangelo Masarati" <ando@sys-net.it>]

> Yes, I think it's a good idea, just don't have the time to move it.

I might be able to work on this and similar stuff (in xmas vacations?). 
I'd consider that and similar stuff as overlays in the sense that they can
be stacked in the operation sequence only if required; what I'm thinking
about is a sort of a "hide" flag for special overlays that are really just
modules of the frontend/backends and that do not require to be loaded. 
replication could be another example, in this case of a backend overlay. 
They wouldn't be explicitly loadable via slapd.conf, but rather by somehow
requiring the related feature.  Replication would be triggered by the
"updatedn" directive; SLAPI by the "plugin" directive, and so.  The
"advantages" would essentially be cleaner code, and, in both cases, a much
cleaner separation of frontend and backend stuff,  resolving many of the
isues I'm currently facing with global overlays getting data only in a
partially consistent state.

p.

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


-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497