Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44485 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35824 invoked from network); 26 Jun 2009 19:40:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jun 2009 19:40:07 -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 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:33881] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/25-08868-314254A4 for ; Fri, 26 Jun 2009 15:40:05 -0400 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id E5C7DE12BB for ; Fri, 26 Jun 2009 12:29:06 -0700 (PDT) Received: from [192.168.16.83] ([192.168.16.83]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 12:40:32 -0700 Message-ID: <4A452411.7060900@zend.com> Date: Fri, 26 Jun 2009 12:40:01 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Michael Shadle CC: PHP Development References: <4A451E00.4090409@zend.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Jun 2009 19:40:32.0496 (UTC) FILETIME=[F7D06700:01C9F695] Subject: Re: [PHP-DEV] PHP-FPM is now BSD-compatible, I believe there was interest in integrating it/portions of it into PHP core? From: stas@zend.com (Stanislav Malyshev) Hi! > I believe that Dmitry was interested in actually *replacing* the FastCGI > SAPI with it (or at least patching it 100%) - the configuration options > and "userland" usage of it is where I am not sure how it would "bundle" > with PHP properly. It uses a different config syntax (not ini compatible) Well, current fcgi doesn't have too many ini values. > 1) Merge it 100% into PHP core (I see some issues with how to configure > it then) > 2) Merge all the core changes required for it to work as a PECL module > (so people can use it via PECL if they wish and configure it how they > want, and all config file syntax changes and such can be done inside of > PECL) > 3) Make it 100% PECL (don't think this is possible as it needs too many > things inside of the core of PHP to be changed) > 4) Keep it as a patch (lower adoption, current status quo) When we talk about "core" changes - what these changes are? I.e. does it need any changes besides the usual SAPI stuff and if so, which ones? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com