Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29566 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36389 invoked by uid 1010); 19 May 2007 18:22:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 36373 invoked from network); 19 May 2007 18:22:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 May 2007 18:22:25 -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.114 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 63.205.162.114 unknown Windows 2000 SP4, XP SP1 Received: from [63.205.162.114] ([63.205.162.114:12010] helo=us-ex1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 31/51-22488-E504F464 for ; Sat, 19 May 2007 14:22:24 -0400 Received: from [127.0.0.1] ([192.168.17.30]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 19 May 2007 11:22:20 -0700 Message-ID: <464F4056.1050500@zend.com> Date: Sat, 19 May 2007 11:22:14 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Cristian Rodriguez CC: internals@lists.php.net References: <464DCB8C.90803@chiaraquartet.net> <7d5a202f0705181813l221248cdu85197a82a1ee4227@mail.gmail.com> <464E5856.5000901@zend.com> <7d5a202f0705190242haca6793i81564178f6d8ed21@mail.gmail.com> In-Reply-To: <7d5a202f0705190242haca6793i81564178f6d8ed21@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 May 2007 18:22:20.0193 (UTC) FILETIME=[A3520910:01C79A42] Subject: Re: [PHP-DEV] potential solution to user streams + allow_url_include=off From: stas@zend.com (Stanislav Malyshev) > The issue with this remote url include thingy is that is hard to find > a valid use case ..does anyone has a **real** one ? why it was I believe there is. > introduced in the first place..?? no, Im not talking about crippling As I already said, it was never introduced. What was introduced is stream functionality in filesystem layer that allows remote access. Since include uses filesystem layer that means include can do that too. > introduction..my intention is only to make people think if the hassle > of adding new ini directives (like allow_url_include) or functions is > worth. maybe with PHP6 this issue can be addressed from it's roots > instead of adding yet another workaround. How do you propose to address that (taking into account what I said above)? -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/