Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46010 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96558 invoked from network); 10 Nov 2009 20:28:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2009 20:28:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.117 us-mr1.zend.com Linux 2.4/2.6 Received: from [63.205.162.117] ([63.205.162.117:40852] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/FA-38546-EECC9FA4 for ; Tue, 10 Nov 2009 15:28:31 -0500 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id 8A5D3E11E9; Tue, 10 Nov 2009 12:26:19 -0800 (PST) Received: from [192.168.16.66] ([192.168.16.66]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Nov 2009 12:28:27 -0800 Message-ID: <4AF9CCEA.1030500@zend.com> Date: Tue, 10 Nov 2009 12:28:26 -0800 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Greg Beaver CC: internals@lists.php.net, Christian Schneider , Lukas Kahwe Smith References: <413588E2-8AC8-49F7-B7BF-97BEFB0A71E4@pooteeweet.org> <4AF9A03E.8000207@cschneid.com> <4AF9AE1A.9000005@zend.com> <4AF9C589.3090604@chiaraquartet.net> In-Reply-To: <4AF9C589.3090604@chiaraquartet.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Nov 2009 20:28:27.0291 (UTC) FILETIME=[5BEB0EB0:01CA6244] Subject: Re: [PHP-DEV] Re: alternative to the fopen() hack in autoloaders From: stas@zend.com (Stanislav Malyshev) Hi! >> This would break security distinction between file ops and include ops, >> when URLs are allowed for open but not include. Additional thing - it probably would be a problem for bytecode caches, since they'd have to: a. watch all file opens, in case some of these will later be used for include b. somehow be able to get filename back from open stream to get the cached file. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com