Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13545
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <417ED858.3040004@caraveo.com>
Date: Tue, 26 Oct 2004 16:06:00 -0700
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@php.net>
CC: Wez Furlong <kingwez@gmail.com>, internals <internals@lists.php.net>,
        Andi Gutmans <andi@zend.com>, Marcus Boerger <helly@php.net>
References: <4e89b4260410261513911b5ae@mail.gmail.com> <Pine.LNX.4.58.0410261522240.1390@t42p.lerdorf.com>
In-Reply-To: <Pine.LNX.4.58.0410261522240.1390@t42p.lerdorf.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] dl() unload / module shutdown issue still unresolved
From: shane@caraveo.com (Shane Caraveo)

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.

Shane