Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46280 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33523 invoked from network); 4 Dec 2009 14:07:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Dec 2009 14:07:14 -0000 Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:38545] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/13-18655-097191B4 for ; Fri, 04 Dec 2009 09:07:13 -0500 Received: from [192.168.3.109] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTPSA id 8E7D2BFA085; Fri, 4 Dec 2009 17:07:09 +0300 (MSK) Message-ID: <4B191787.1080201@daylessday.org> Date: Fri, 04 Dec 2009 17:07:03 +0300 User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: php-dev References: <4B190660.2050107@daylessday.org> <1259935098.2639.98.camel@guybrush> In-Reply-To: <1259935098.2639.98.camel@guybrush> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] FPM is available in a separate SVN branch From: tony@daylessday.org (Antony Dovgal) On 04.12.2009 16:58, Johannes Schlüter wrote: > How big would be the impact in regards to BC and stuff for merging it > back in 5_3? If i read the svn log correct it's just a SAPI ... so > adding it might be low risk as it only affects people using it. That's right, it's a separate SAPI, it doesn't affect anything beyond sapi/fpm in any way. > Is it related to the CGI SAPI codewise? Yes, it uses modified versions of cgi_main.c and fastcgi.c/.h. > If yes: would there be plans to > merge it in some way or would we have to fix bugs in CGI, FPM and > probably CLI which all have the same roots? I'm planning to remove some more unused/unnecessary code from fpm_main.c. I guess this will somewhat reduce the amount of porting between the "copy" and original file. -- Wbr, Antony Dovgal --- http://pinba.org - realtime statistics for PHP