Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29285 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16310 invoked by uid 1010); 7 May 2007 18:54:22 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16293 invoked from network); 7 May 2007 18:54:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2007 18:54:22 -0000 Authentication-Results: pb1.pair.com header.from=david.coallier@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=david.coallier@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.244 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: david.coallier@gmail.com X-Host-Fingerprint: 209.85.132.244 an-out-0708.google.com Received: from [209.85.132.244] ([209.85.132.244:35469] helo=an-out-0708.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F5/E4-56106-BD57F364 for ; Mon, 07 May 2007 14:54:21 -0400 Received: by an-out-0708.google.com with SMTP id d31so143121and for ; Mon, 07 May 2007 11:54:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=r2FEY7zPpC7haoTvioyTMrlh862Yr46+prlj8PdqMU6V6fmbxB3Ig8lzCuJtQP750yV8IWzlpgcK7j+wEyYoBtY/RuPlyxN3nxnKMkgCPwQ/U2pRXXeXmHH9LbH7d3pw8oDfCi2g/CKQjqdIJU92Qv94A6B0w5q59F0H8mN6Frc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=kz/h6gyk30cUIgXjT77lqo2BLBimClelZ5fm9GYHneorzOulVJoppPLf4EAUmEfkV8jhXEdG2nygz/O/lstiVg+zwDqtQmkOjwXLkgHBWZqF7EycDdG0RDFsR8IWSkSScnNAJT3cJFMkcCXZUFq4+f7WRCZWL5FtubAgOslitm8= Received: by 10.100.202.13 with SMTP id z13mr5092372anf.1178564056356; Mon, 07 May 2007 11:54:16 -0700 (PDT) Received: by 10.101.70.18 with HTTP; Mon, 7 May 2007 11:54:15 -0700 (PDT) Message-ID: Date: Mon, 7 May 2007 14:54:15 -0400 Sender: david.coallier@gmail.com To: "Antony Dovgal" Cc: "Stanislav Malyshev" , "Gregory Beaver" , "Lukas Kahwe Smith" , "Marcus Boerger" , "Edin Kadribasic" , internals@lists.php.net In-Reply-To: <463F7531.90504@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <139872287.20070504170744@marcus-boerger.de> <463B9271.3040009@zend.com> <1348470081.20070504221609@marcus-boerger.de> <463EB3FD.4020009@zend.com> <1062653277.20070507092725@marcus-boerger.de> <463F1930.7030004@pooteeweet.org> <463F1CE6.1020805@zend.com> <463F6DCE.6070002@chiaraquartet.net> <463F7271.4030306@zend.com> <463F7531.90504@zend.com> X-Google-Sender-Auth: dfe3d74c655c49f2 Subject: Re: [PHP-DEV] [RFC] Starting 5.3 From: davidc@php.net ("David Coallier") On 5/7/07, Antony Dovgal wrote: > On 05/07/2007 10:39 PM, Stanislav Malyshev wrote: > >> PHP_Archive-based phar archives will no longer work once > >> allow_url_include is off and user streams wrappers are marked as remote. > >> So, it won't work with 100% of new installations in future PHP versions. > > > > I guess we are solving the wrong problem. We have: > > 1. phar needs script-defined named streams > > 2. Named streams are prohibited by some config option > > 3. Let's pretend this stream is not actually what it is > > 4. Let's create whole new extension for that and put it into main PHP > > Exactly what I said in IRC earlier today. > Both problem and solution look weird. > > > I think this process is wrong. If we have problem with names streams > > usage in apps, we should seek solutions there, not invent modules just > > to work around the problem we ourselves create. What happens we need > > next application using named streams? Another extension into main PHP > > source whose purpose is to duplicate PHP code and work around our own > > security model? > > > -- > Wbr, > Antony Dovgal > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Ok just so there's no confusion.. Here's 2 examples why PEAR and phar are both useful (If you need more detailed examples (file names, etc I can also draw up something) 1) Phar: You can use phar for instance if you deploy all your own scripts, etc. A normal application without third party libraries bundled (Otherwise of couse you can store your third script in your phar and just make a new release when the third-script updates) etc. The idea of the phar is to make it easy to deploy. Which is good. 2) Pear: Pear has channels which make it really easy to deploy applications that are depending on different channels (third party scripts) which make it easy to both install and udpate. You wrap your application in your package name which you distribute through the SOMENAME.com channel, then you can also use another channel (the third party script) by using channel-discover and download/easy update the third-party scripts using pear upgrade SOMEOTHERCHANNEL.com's package name. -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18