Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Philippe M. Chiasson
Geoffrey Young wrote: anyway, the code is meant to be more of an illustration than a module you would want to use in production, but still... And it suffers from a pretty terrible dependency on the internal structure of the module you are peeking at to be static. You are basically defining a copy

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Geoffrey Young
>> anyway, the code is meant to be more of an illustration than a module you >> would want to use in production, but still... > > > And it suffers from a pretty terrible dependency on the internal structure > of the module you are peeking at to be static. You are basically defining > a copy of t

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Philippe M. Chiasson
Geoffrey Young wrote: The only suggested way to achieve something like that is to piggyback configuration directive. If you have a module that wants to know the value of DirectoryIndex, for instance, you could implement a mod_perl handler that supports a DirectoryIndex directive, and return DECLI

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Geoffrey Young
> The only suggested way to achieve something like that is to piggyback > configuration directive. If you have a module that wants to know the > value of DirectoryIndex, for instance, you could implement a mod_perl > handler that supports a DirectoryIndex directive, and return DECLINED, > passing

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Stas Bekman
Philippe M. Chiasson wrote: Stas Bekman wrote: dorian wrote: is there currently a prescribed method for accessing the "current" configuration for a request, i.e., after all the merges have been done, at the particular stage a request is in? that is, if i want to access the current valid DirectoryI

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Philippe M. Chiasson
Stas Bekman wrote: dorian wrote: is there currently a prescribed method for accessing the "current" configuration for a request, i.e., after all the merges have been done, at the particular stage a request is in? that is, if i want to access the current valid DirectoryIndex when a PerlTypeHandler

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Stas Bekman
dorian taylor wrote: I know you can do: $r->location_merge('container_string'); which forces an earlier merge, but I'm not sure it'll affect the conf tree shown by Apache::Directive. Have you tried looking at the C code to see whether there is a C API for that? well, there's $r->per_dir_config a

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread dorian taylor
> I know you can do: > $r->location_merge('container_string'); > which forces an earlier merge, but I'm not sure it'll affect the conf > tree shown by Apache::Directive. Have you tried looking at the C code to > see whether there is a C API for that? well, there's $r->per_dir_config and $r->requ

Re: [mp2] access to merged external (non-perl) config directives

2004-07-14 Thread Stas Bekman
dorian wrote: is there currently a prescribed method for accessing the "current" configuration for a request, i.e., after all the merges have been done, at the particular stage a request is in? that is, if i want to access the current valid DirectoryIndex when a PerlTypeHandler is called, after pos

[mp2] access to merged external (non-perl) config directives

2004-07-13 Thread dorian
is there currently a prescribed method for accessing the "current" configuration for a request, i.e., after all the merges have been done, at the particular stage a request is in? that is, if i want to access the current valid DirectoryIndex when a PerlTypeHandler is called, after possible VirtualH