> The assumption is that overlays are configured after their parent
> backends, so be_acl is already fully initialized before the overlay gets
> control.
not currently... unless we move acl_append( ...be_acl, global_acl ) to an
earlier point.
> For the proxy cache there's barely any need to keep a separate BackendDB
> structure, except for the SLAP_DBFLAG_NO_SCHEMA_CHECK on the internal
> database. I suppose if we added a NO_SCHEMA_CHECK flag to the Operation
> somewhere, we could get rid of this.
cm->db.bd_info is still needed and no better placeholder than cm->db.
- Jong-Hyuk