Re: [mp2] ideas for pre-loading modules before server startup?

On Thu, 15 Jul 2004, Stas Bekman wrote:

> Stas Bekman wrote:
> > I see, that Philippe has found a nice trick to load Apache::PerlSections
> > at the server startup, w/o actually doing that explicitly. He deployed
> > the handlers automatic autoloading. Though this trick doesn't work for
> > other things. I want to move the pre-loading of APR::Error to the the
> > internals of mp2, but since it may reside in the Apache2/ subdir, we
> > can't try loading it, before a user loads Apache2.pm. Which may not
> > happen at all. And we may need to load other modules in the future as
> > well (e.g. things that we discussed before - load Apache::RequestRec
> > before handing user $r).
> >
> > We can't force on user loading Apache2, since he may want to adjust
> > @INC, before Apache2.pm is loaded.
> >
> > I thought that moving APR/* packages out of Apache2/ will solve that
> > problem, removing the dependancy on Apache2.pm, but as Joe suggested
> > it's probably not the best approach, due to versioning...
> >
> > So if you have ideas how to resolve that issue, I'm all ears.
>
> So any ideas? We need to preload APR::Error to start with.

I'm sure I don't appreciate all the issues involved, but
just to backtrack a moment - for the particular case of
APR::Error, what is that latest point at which it should be
loaded? For example, would it be enough to load APR::Error
when other modules are loaded (within an XSLoader,
perhaps?). Or is this too late? Or not possible?

-- 
best regards,
randy