[Date Prev][Date Next]
Re: ITS#3781 back-config doesn't work with xxx
>> Is there a description somewhere of what it means to support
>> back-config? For example, how would back-perl do it? The admin can
>> write a Perl config() function which defines new slapd.conf directives;
>> only a few directives are hardcoded.
> I suggest that backends like back-perl just define a "perl-" directive
> that allows arbitrary length and args which are passed to the
> user-provided config routine. I see it a bit harder to implement "emit"
> in a consistent way, though.
That implies that you'll only have a single attributeType for back-perl
config directives. I guess it would work, but it pretty much means
implementing a table-driven config engine in perl, to manage things from
there (assuming you want to support LDAP_MOD_DELETE and have full
runtime reconfigurability). Or maybe a set of perl hooks for
constructing schema tables that can be passed to
config_register_schema(), so that the perl module can properly define
its config items. I think either way this is a fair chunk of perl XS code.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/