> I don't know about a compile-time option personally. I can just see it > causing lots more problems than solving anything. It would introduce a > huge number of basically different mod_perls, with different behaviour > for the same user code, making bug tracking et all even more > problematic.
well, I kinda agree. however, in apache 1.3 land users did have the option of running mod_perl _after_ C handlers. in fact, I can remember at least one person who specifically asked to make mod_perl run _after_ a C trans hander, kind of like a fallback. of course, that was possible in 1.3 with ClearModuleList and/or shifting mod_perl lower in in the configuration order at compile time. so, making it a compile-time option is kinda making it like it used to be. at least that's my thought at the moment :) > > Making it a startup configuration should be possible, IMO. Only if that > turns out to be impossible, I'd make it a compile-time option. I don't think it's impossible, but I think it will be hard - we'd basically need to change the nOrder value in the each hook structure at some point then call apr_hook_sort_* manually. I might be able to do this when some directive is parsed or it may need to be a request-time operation - I can't be sure without trying it first. but the whole thing gives me the willies, and I feel like we'd be introducing some magic that might add some instability for very little value. but stay tuned :) --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
