Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:999 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78964 invoked from network); 21 Apr 2003 18:33:48 -0000 Received: from unknown (HELO mail.modwest.com) (216.129.251.30) by pb1.pair.com with SMTP; 21 Apr 2003 18:33:48 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.modwest.com (Postfix) with ESMTP id 2B7F740F5CEA for ; Mon, 21 Apr 2003 12:33:48 -0600 (MDT) Received: from mail.modwest.com ([127.0.0.1]) by localhost (marshall.modwest.com [127.0.0.1]) (amavisd-new) with ESMTP id 16238-14 for ; Mon, 21 Apr 2003 12:33:47 -0000 (MDT) Received: from [10.0.0.137] (unknown [69.24.111.150]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.modwest.com (Postfix) with ESMTP id 9D6E740F58B8 for ; Mon, 21 Apr 2003 12:33:47 -0600 (MDT) Date: Mon, 21 Apr 2003 12:35:54 -0700 To: internals@lists.php.net Message-ID: <422283437.1050928554@[10.0.0.137]> X-Mailer: Mulberry/3.0.3 (Win32 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new amavisd-new-20020630 Subject: Touching certain globals for making a deprecated/excluded/ignored modules/extension list From: mloftis@modwest.com (Michael Loftis) Since we can't really be modifying 2k+ customers php.ini files every time the core moves something from being shared to static what I want to do is make an 'ignore dynamic loading' or dynamic extension load excludes or however you want to term it. If there's interest I'll contribute it back, but if not then I'll hack it up so it works in our case. Specifically my problem is I want to touch _php_core_globals and add an extra entry to that struct, but I want to make sure that by doing that I'm not going to cause any serious problems (provided I prefix it with something meaningful to help avoid namespace collisions). Obviously I'll be touching php_dl, as well as a couple other places probably, but none of those really worry me because I can add/remove code w/o changing API structs. Does the Zend Optimizer (one of the modules we make extensive use of) depend on _php_core_globals, or anything else for that matter that the core team knows of? I just don't want to code up something and then find out it breaks things. TIA for any info you all can provide. More on what I want to do: Basically make a comma seperated list that lives in a config var (or file in our case here at modwest) that gets loaded on startup. When php_dl is called to dynamically load an extension it checks to see if the extensions filename (stripping any leading path information) is in this list, if it is it returns w/o an error, possibly logging a warning that 'module yyyy is in list of excluded modules' I welcome any comments anyone may have as well. -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting