Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13546 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55701 invoked by uid 1010); 26 Oct 2004 23:22:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 55621 invoked from network); 26 Oct 2004 23:22:29 -0000 Received: from unknown (HELO colo.lerdorf.com) (66.198.51.121) by pb1.pair.com with SMTP; 26 Oct 2004 23:22:29 -0000 Received: from rasmus2.corp.yahoo.com (rasmus2.corp.yahoo.com [207.126.233.18]) by colo.lerdorf.com (8.13.1/8.13.1/Debian-15) with ESMTP id i9QNMOWN013159; Tue, 26 Oct 2004 16:22:24 -0700 Date: Tue, 26 Oct 2004 16:22:19 -0700 (PDT) X-X-Sender: rasmus@t42p.lerdorf.com To: Shane Caraveo cc: Wez Furlong , internals , Andi Gutmans , Marcus Boerger In-Reply-To: <417ED858.3040004@caraveo.com> Message-ID: References: <4e89b4260410261513911b5ae@mail.gmail.com> <417ED858.3040004@caraveo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] dl() unload / module shutdown issue still unresolved From: rasmus@php.net (Rasmus Lerdorf) 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