Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45538
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender)
Message-ID: <4AA764F1.9070508@zend.com>
Date: Wed, 09 Sep 2009 01:18:57 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: internals@lists.php.net
References: <99cf22520909081652v29a9ea56q33882849cce3081e@mail.gmail.com> <4AA6F06C.4020008@lerdorf.com> <4AA75C9F.3090605@iki.fi> <4AA75EFF.5040800@zend.com> <4AA760CC.9060203@iki.fi>
In-Reply-To: <4AA760CC.9060203@iki.fi>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [sapi] PHP-FPM (FastCGI Process Manager), by Andrei
 Nigmatulin - upstream Y/n?
From: stas@zend.com (Stanislav Malyshev)

Hi!

> Very good point. And I did consider only merging the _good_ parts of 
> this thing. I haven't had time to check the code yet at all (quite busy 
> at work right now) but there are some stuff it does we haven't generally 
> considered the "job of PHP" before. The list of them is here:
> 
> http://php-fpm.org/What_is_PHP-FPM

Exactly. That's why I don't have a problem of it being a separate SAPI - 
we have about 20, what harm could one more do? :) It's much safer this 
way. And if we discover merging into sapi/cgi really makes sense - at 
least we'd have code that already works with php, plays by php rules, 
etc. so it'd be much easier and safer.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com