Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36455 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54532 invoked from network); 24 Mar 2008 20:46:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Mar 2008 20:46:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 204.11.219.139 mail.lerdorf.com Received: from [204.11.219.139] ([204.11.219.139:44385] helo=mail.lerdorf.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/67-20329-81318E74 for ; Mon, 24 Mar 2008 15:46:17 -0500 Received: from trainburn-lm.corp.yahoo.com (trainburn-lm.corp.yahoo.com [207.126.233.11]) (authenticated bits=0) by mail.lerdorf.com (8.14.2/8.14.2/Debian-3) with ESMTP id m2OKkD5h022848; Mon, 24 Mar 2008 13:46:13 -0700 Message-ID: <47E81315.4060601@lerdorf.com> Date: Mon, 24 Mar 2008 13:46:13 -0700 User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Stanislav Malyshev CC: George Wang , internals@lists.php.net References: <47E80EB9.60900@litespeedtech.com> <47E81136.3040308@zend.com> In-Reply-To: <47E81136.3040308@zend.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.92.1/6374/Mon Mar 24 12:56:49 2008 on colo.lerdorf.com X-Virus-Status: Clean Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP distribution? From: rasmus@lerdorf.com (Rasmus Lerdorf) Stanislav Malyshev wrote: > Hi! > >> I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is >> one of the top PHP SAPI being used in production environment. And >> LiteSpeed SAPI has the combination of best performance, configuration >> flexibility via .htaccess and enhanced security with SuEXEC. > > I did not look into the SAPI yet, but if it works good and conforms to > PHP project reqs (code standards, license, etc.) then I see no reason > not to add it, provided the popularity data and the fact that we have > much more exotic SAPIs in the core. Well, popularity-wise it has about 0.003% of the web server market. So I wouldn't put too much stock in that. We also have yet to ever see a user request for it. 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. -Rasmus