> 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 it back to mod_autoindex. That module would need to merge
> directory indexes in the same way mod_autoindex does it, but that's the 
> core of the problem.

while that's a trick I have used often, it's not the _only_ way.  see recipe
 8.14 in the cookbook, along with the code from

http://www.modperlcookbook.org/code/ch08/Cookbook-LanguagePriority-0.01.tar.gz

which essentially allows you to peek into a module's private configuration,
which I'm pretty sure is the merged version at this point, but it's been a
while since I've really tested that code out.

anyway, the code is meant to be more of an illustration than a module you
would want to use in production, but still...

and bonus karma points to anyone who groks the latin phrase on page 299 ;)

--Geoff

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to