Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45535 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46680 invoked from network); 9 Sep 2009 07:59:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Sep 2009 07:59:38 -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:54925] helo=us-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0E/A4-26597-86067AA4 for ; Wed, 09 Sep 2009 03:59:37 -0400 Received: from us-gw1.zend.com (us-ex1.zend.net [192.168.16.5]) by us-mr1.zend.com (Postfix) with ESMTP id 9EBC0E11E9; Wed, 9 Sep 2009 00:46:20 -0700 (PDT) Received: from [192.168.27.1] ([192.168.27.1]) by us-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Sep 2009 00:53:36 -0700 Message-ID: <4AA75EFF.5040800@zend.com> Date: Wed, 09 Sep 2009 00:53:35 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: jani.taskinen@iki.fi CC: Rasmus Lerdorf , dreamcat four , internals@lists.php.net, jvlad , Dmitri Dmitrienko References: <99cf22520909081652v29a9ea56q33882849cce3081e@mail.gmail.com> <4AA6F06C.4020008@lerdorf.com> <4AA75C9F.3090605@iki.fi> In-Reply-To: <4AA75C9F.3090605@iki.fi> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Sep 2009 07:53:36.0629 (UTC) FILETIME=[A2F7FA50:01CA3122] Subject: Re: [PHP-DEV] [sapi] PHP-FPM (FastCGI Process Manager), by Andrei Nigmatulin - upstream Y/n? From: stas@zend.com (Stanislav Malyshev) Hi! > As separate SAPI, wouldn't it duplicate a LOT of code, basically for > nothing? I'd rather see the good parts of this merged into the > one-and-only sapi/cgi/ code instead of creating yet another SAPI nobody > maintains for real. If the code will be really the same exactly, then maybe it can be just reused (e.g. functions, etc.)? If not, then somewhat similar code I don't think is a problem if it's maintained, and if it's not then better have unmaintaned separate SAPI then unmaintained pieces of code inside of one of most used SAPIs :) In general, I'd consider changing sapi/cgi adding new potentially unstable hode rather high-risk, unless it can be very well isolated. sapi/cgi runs quite a lot of code... -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com