Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37608 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94192 invoked from network); 12 May 2008 17:31:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 May 2008 17:31:48 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.162 mail.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.162] ([212.25.124.162:52955] helo=mx1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/E0-22594-20F78284 for ; Mon, 12 May 2008 13:31:48 -0400 Received: from us-ex1.zend.com ([192.168.16.5]) by mx1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 May 2008 20:32:48 +0300 Received: from [192.168.16.217] ([192.168.16.217]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 May 2008 10:32:44 -0700 Message-ID: <48287EFC.4090205@zend.com> Date: Mon, 12 May 2008 10:31:40 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Hector Santos CC: internals@lists.php.net References: <4824219D.3070806@isdg.net> <4824EEAA.3080901@isdg.net> In-Reply-To: <4824EEAA.3080901@isdg.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 May 2008 17:32:44.0695 (UTC) FILETIME=[30155270:01C8B456] Subject: Re: [PHP-DEV] Extension_Dir: Proposal to offer multi-directory DLL loading From: stas@zend.com (Stanislav Malyshev) Hi! > Let me simply ask, do you think there is technical merit (worth while) > to create a patch which offers multi-directory DLL loading support for > the PHP.INI extension_dir= option? extension is an one-time configuration directive. Since it allows full path now, how hard would it be to get it right with full path? Multiple paths may contain some dangerous pitfalls - like, what happen if extension is in multiple paths, and in some it's not compatible (wrong version/debug/ts)? What if you have some old version lying around in fifth path, and you had new version in first path, but somehow permissions got mangled and it's not readable, so wrong version is loaded? Etc., etc. - it seems to have potential for many unpleasant moments. > 1) Reduce extension DLL (non-PHP related) dependency issues, How? I'd say, if you have extension A using foo.dll, and extension B using foo.dll, and they live in different directories, don't you now have to maintain two copies of foo.dll instead of one? > 2) Better support for PHP integration with Application Servers, and Here I'd like to hear more - how it helps PHP and Application Servers? > 3) Better support for security isolation, sand-boxing applications I'm not sure how giving multiple places to put security-sensitive stuff (extension has access to everything) improves sandboxing, could you explain? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com