> -----Original Message-----
> From: Christian Gilmore [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 2:00 PM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: RE: [RFC] Apache::BlockSymLinks 0.1
>
>
>
> Geoff, et al:
>
> I've toyed with ModuleConfig, and it is really cool, but I
> was under the
> impression that people stayed away from using it since it appears to
> require a recompile of mod_perl for every module that inserts a new
> directive into the list. That's why I assumed the use of
> PerlSetVar was
> much more popular than ModuleConfig.
I think PerlSetVar is more popular because it's easier to implement and
doesn't require much effort. ModuleConfig.pm is a bit more complex, but it
is still just straight perl and doesn't require XS to implement. It depends
on your needs, though - I wouldn't use it when you only need a few config
directives but I might prefer it to a file-based config like BlockSymLinks
uses.
as far as the recompiling of mod_perl goes, that doesn't make sense to me.
Apache::Dispatch uses ModuleConfig for all it's parameters and you should be
good to go with just the typical make stuff.
--Geoff
>
> Regards,
> Christian
>
> On Fri, 2 Feb 2001, Geoffrey Young wrote:
> > you may want to look into Apache::ModuleConfig to see how
> you can create
> > directives without the need for a separate config file.
> >
> > for instance:
> > SymLinkRule Deny .*
> >
> > it's pretty easy and probably a bit cleaner in this case
> (since I suspect
> > that you moved to a config file since PerlSetVar just
> didn't fit the bill
> > for the syntax you wanted). just see chapter 8 of the Eagle book
>
