Quoting Geoffrey Young ([EMAIL PROTECTED]):
>
>
> > In the process, I been wondering is it possible to peek at the
> > configuration directives/values of other modules (both Perl and C)
> > via mod_perl?
>
> sort of - in both instances you have to do some tricks and break
> encapsulation. for Perl you have to get the module's configuration using
> Apache::ModuleConfig->get($r, package) where package- is the class of the
> class in question. for C it's a bit trickier and may not work on all
> platforms (it doesn't on windows) but you can check the archives for Doug's
> example of getting mod_auth's AuthName directive if you really want to.
>
> basically, though, the data you are after is private and should only be
> retrieved via the public interface. but this is Perl, so you are more asked
> to play fair than you are required, and mod_auth doesn't have an
> interface...
I was looking over the mod_info source code, so I knew it could be done.
I just didn't know if mod_perl provided an interface. And rather than
request a URL which invoked mod_info, getting back the HTML, parsing
through it....you get the idea, and so on and so forth, I thought
that information "should" be available to a mod_perl handler via the
mod_perl interface in a more or less object oriented manner.
It's kinda like writing mod_info as a mod_perl handler, only allow the
handler to get the data in an object oriented manner from the mod_perl
interface.
