Return-Path: Mailing-List: contact modperl-help@apache.org; run by ezmlm Delivered-To: mailing list modperl@apache.org Received: (qmail 57591 invoked from network); 2 Feb 2001 19:41:39 -0000 Received: from corpex.laserlink.net (208.216.91.202) by h31.sny.collab.net with SMTP; 2 Feb 2001 19:41:39 -0000 Received: by corpex.laserlink.net with Internet Mail Service (5.5.2650.21) id ; Fri, 2 Feb 2001 14:42:07 -0500 Message-ID: From: Geoffrey Young To: 'Christian Gilmore' Cc: "'brabec@ncsu.edu'" , modperl@apache.org Subject: RE: [RFC] Apache::BlockSymLinks 0.1 Date: Fri, 2 Feb 2001 14:41:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > -----Original Message----- > From: Christian Gilmore [mailto:cgilmore@corp.tivoli.com] > Sent: Friday, February 02, 2001 2:00 PM > To: Geoffrey Young > Cc: 'brabec@ncsu.edu'; modperl@apache.org > 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 >