Re: request hook ordering

----- Original Message ----- 
From: "Stas Bekman" <stas@xxxxxxxxxx>
To: "Geoffrey Young" <geoff@xxxxxxxxxxxxxxxxxxx>


> Geoffrey Young wrote:
> > I've brought it up before, but it looks like users are having real
problems
> > with the way 2.0 hooks modules into the request phases.
> >
> > in 1.0, module order was determined by compile-time ordering or
> > LoadModule/ClearModuleList/AddModule, neither of which exist in 2.0,
where
> > Apache chose the HOOK_FIRST/HOOK_MIDDLE/HOOK_LAST approach.
> >
> > the issue is that for mod_perl to be effective, it really needs to get
first
> > crack at the phases.  for instance, currently a PerlTransHandler
wouldn't be
> > guaranteed to run at all if another module (say, mod_proxy) got there
first.
> >  while there are some occasions where you might want mod_proxy there
first,
> > they are typically rare in mod_perl applications.
> >

Maybe I'm missing something, but it doesn't seem like such a problem.  If I
make my own module DSO in C and  I add the hook when the module loads
(LoadModule) for TransHandler, and I'm using compiled-in mod_proxy, I'll
have the same issue.  Frankly, even if they're both compiled in, I
potentially have the same issue...   And I'm sure that the httpd-dev people
have thought of this.

Just my $0.02...

  Issac