Re: dl() unload / module shutdown issue still unresolved
| From: | Rasmus Lerdorf | Date: | Tue, 26 Oct 2004 23:22:19 +0000 |
| Subject: | Re: dl() unload / module shutdown issue still unresolved | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-13546@lists.php.net to get a copy of this message | ||
On Tue, 26 Oct 2004, Shane Caraveo wrote:
> Rasmus Lerdorf wrote:
> > On Tue, 26 Oct 2004, Wez Furlong wrote:
> >
> >>It should be safe to never ever dlclose() a module.
> >
> >
> > Do you mean never to dlclose() a module loaded via dl() at request time or
> > do you mean that in general it should be safe to never dlclose() a module
> > even if it came in via an extension line in the php.ini file? The former
> > is likely a true statement, but the latter is definitely not.
> >
> > -Rasmus
>
> It's exactly how other languages deal with binary extensions, once
> loaded, never unload, even between requests. That approach would fix
> and greatly simplify dl for php (note I haven't looked at dl code in
> more than a year so I could be speaking out of my ass). The double pass
> that Apache could be handled by having php_apache avoid processing
> extensions on the first pass.
Then we would potentially be throwing bogus syntax errors since the
extension handling a particular conf directive embedded in an Apache conf
file wouldn't be there.
-Rasmus