I think we should go with get_config first of all, so we have the Apache like functionality and later on we can provide a shortcut with syntax sugar.
So we start with: my $dir_cfg = $self->get_config($s, $r->per_dir_config); my $srv_cfg = $self->get_config($s);
And then we can have something like headers_out-like (APR::Table) interface, though read-only.
$parse_headers_is_on = $dir_cfg->perl_options->get('ParseHeaders'); $parse_headers_is_on = $dir_cfg->perl_options->{'ParseHeaders'}; %srv_perl_options = %{ $srv_cfg->perl_options() };
What do you think?
coolio - APR::Table was what I had in mind.
the only difference I was trying to suggest is that, if possible, it would be nice to have a generic interface for all directives. however, I guess this isn't really practical since the majority of the directives contain data private to modules other than core.
so, yeah, I think your suggestion works best :)
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
