Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44480 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27878 invoked from network); 26 Jun 2009 19:14:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jun 2009 19:14:11 -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:33879] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/73-08868-20E154A4 for ; Fri, 26 Jun 2009 15:14:11 -0400 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id 590D2E12BB for ; Fri, 26 Jun 2009 12:03:15 -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:14:40 -0700 Message-ID: <4A451E00.4090409@zend.com> Date: Fri, 26 Jun 2009 12:14:08 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Michael Shadle CC: PHP Development References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Jun 2009 19:14:40.0935 (UTC) FILETIME=[5B02FB70:01C9F692] 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! > It would be great if someone would examine the impact of adopting it > as the FastCGI SAPI replacement or looking at what hooks are required > to get it in and perhaps keep the "userland" stuff in PECL... Why it needs to replace existing fcgi SAPI? I would think it is better to have it just as another SAPI - isn't it possible? I understand (please correct me if I'm wrong) that php-fpm feature set is different from what fcgi SAPI now does - php-fpm manages its own processes, etc. which may be not what some FCGI drivers expect. I think it is possible to add it as SAPI for HEAD at any time, and once 5.3 is out of the release freeze, add it to 5.3 as well. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com