httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <c...@force-elite.com>
Subject Re: Sharing Config Commands
Date Thu, 26 May 2005 01:02:46 GMT
Joshua Slive wrote:
> On Wed, 25 May 2005 14:10:38 -0700, "Paul Querna" <chip@force-elite.com>
> said:
> 
>>Currently, you can have multiple modules share a single directive, if
>>they return DECLINE_CMD, instead of NULL.  The problem is that this
>>behavior depends on the order of the modules being loaded.
>>
>>I am attempting to have my mod_svn_view share the 'SVNParentPath'
>>directive with mod_dav_svn.  Since mod_dav_svn is out of my control, it
>>always returns NULL for SVNParentPath.  If mod_svn_view is loaded
>>_after_ mod_dav_svn, it works, since my module returns DECLINE_CMD.
>>mod_dav_svn will then consume it after me and return NULL.
>>
>>This is caused by the linked list of modules being in reverse order of
>>the LoadModule directive.
>>
>>I think we want to encourage that the order of LoadModule doesn't
>>matter.  I also think any module should be able to receive the values
>>for any configuration command.
> 
> 
> Why don't you just explicitly specify that your module's hook should run
> before the one for mod_dav_svn?

For configuration directives?

Directives are not hooks.  I already am set to run before mod_dav in the
handler hooks, but this has no use if I cannot receive the configuration
values.

Mime
View raw message