Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36456
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <47E81523.4010505@zend.com>
Date: Mon, 24 Mar 2008 13:54:59 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: George Wang <gwang@litespeedtech.com>, internals@lists.php.net
References: <47E80EB9.60900@litespeedtech.com> <47E81136.3040308@zend.com> <47E81315.4060601@lerdorf.com>
In-Reply-To: <47E81315.4060601@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP
 distribution?
From: stas@zend.com (Stanislav Malyshev)

> You are right though, that we have other really odd SAPIs in the core, 
> but that is mostly a result of never having figured out how build a sapi 
> module standalone.  Most of these really do belong in pecl if we could 
> solve the standalone issue.

Right, but if we didn't solve it - why we have pi3web or webjames (what 
that is anyway?) and not litespeed? At least litespeed appears on the 
map. As for user request, I think server's vendor request is a user 
request, when PHP is concerned - why have PHP API on a server if not to 
use it? As soon as we have commitment from the support side - and I 
understand we have it here - I see no problem in having this SAPI.
Of course, figuring out how to do SAPI in PECL is a solution too, but is 
anybody working on it?
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com