Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29334 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79702 invoked by uid 1010); 8 May 2007 13:27:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79687 invoked from network); 8 May 2007 13:27:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 May 2007 13:27:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 212.112.227.169 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from [212.112.227.169] ([212.112.227.169:53764] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/A4-10930-4AA70464 for ; Tue, 08 May 2007 09:27:01 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id B4DC2DF0085; Tue, 8 May 2007 15:26:57 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (flottensignalgeber [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12479-01; Tue, 8 May 2007 15:26:55 +0200 (CEST) Received: from [127.0.0.1] (dt0f2n29.tampabay.res.rr.com [24.92.178.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ipx11223.ipxserver.de (Postfix) with ESMTP id 2EA89DF006F; Tue, 8 May 2007 15:26:55 +0200 (CEST) Message-ID: <46407A99.5010907@pooteeweet.org> Date: Tue, 08 May 2007 09:26:49 -0400 User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Stanislav Malyshev Cc: Marcus Boerger , internals@lists.php.net References: <139872287.20070504170744@marcus-boerger.de> <1348470081.20070504221609@marcus-boerger.de> <463EB3FD.4020009@zend.com> <1062653277.20070507092725@marcus-boerger.de> <463ED871.8080606@zend.com> <463F1B3A.3070703@pooteeweet.org> <463F74EA.7030704@zend.com> <1377895609.20070507211530@marcus-boerger.de> <463F8909.6000709@zend.com> <1376921277.20070508103616@marcus-boerger.de> <46406D8A.3010005@zend.com> In-Reply-To: <46406D8A.3010005@zend.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] [RFC] Starting 5.3 From: mls@pooteeweet.org (Lukas Kahwe Smith) Stanislav Malyshev wrote: >> either Greg or me as PHP customers. Nor was Phar designed to solve >> that particular issue alone. It was designed to deliver a stable and >> fast implementation of PHP_Archive that can be bundled into PHP as >> a C extension. > > That's fine, the question is why exactly we need fast implementation of > PHP_Archive that can be bundled into PHP as a C extension. I see only > one reason - to run php code in production out of phar, and I don't > think it's a good idea. Any other reasons? I think it is a good reason. There are plenty of tool-like PHP applications. Not having to "install" these, but just be able to maintain a config file and a single file would be quite nice imho. regards, Lukas