Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47503 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22042 invoked from network); 23 Mar 2010 19:47:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 19:47:46 -0000 Authentication-Results: pb1.pair.com header.from=jerome@loyet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jerome@loyet.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain loyet.net from 74.125.82.42 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 74.125.82.42 mail-ww0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:44115] helo=mail-ww0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 17/0A-03444-1EA19AB4 for ; Tue, 23 Mar 2010 14:47:45 -0500 Received: by wwc33 with SMTP id 33so122009wwc.29 for ; Tue, 23 Mar 2010 12:47:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.93.68 with SMTP id k46mr1442386wef.104.1269373662384; Tue, 23 Mar 2010 12:47:42 -0700 (PDT) In-Reply-To: References: <4BA8EF6F.8010503@daylessday.org> <4BA8F72E.5090701@sci.fi> <4BA8F985.1090109@daylessday.org> Date: Tue, 23 Mar 2010 20:47:42 +0100 Message-ID: <3bea96c41003231247l7d632fc1u3a9f2f5300dd9561@mail.gmail.com> To: Pierre Joye Cc: Antony Dovgal , jani.taskinen@iki.fi, php-dev Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] FPM RFC From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) 2010/3/23 Pierre Joye : > hi Tony, > > On Tue, Mar 23, 2010 at 6:25 PM, Antony Dovgal wrote: > >>> Does it really need to be separate SAPI? I mean, just replace the old sapi/cgi >>> with it? Keep the name 'cgi' though. :) >> >> I don't see any need to touch sapi/cgi at all. >> Keeping both CGI and FastCGI in one SAPI leads to a nasty code mess with lots of >> "if (fcgi_is_fastcgi()) {" as you can now see in cgi_main.c. > > Not sure to follow, are you suggesting to consider FPM as the > sapi/cgi's fastcgi replacement? As Jani is suggesting. > >> sapi/fpm and sapi/cgi now have quite different codebase as we've dropped some stuff >> not pertinent to FastCGI (there might be some leftovers, I'll deal with them later). > > By the way, how portable is it? I don't think it has been tested on > windows (some of the key features are not necessary with IIS/FCGI as > they do it already but could be for other web servers). As far as I know, It's not been tested on windows. It depends on libevent which is available for windows, so porting fpm to windows should not be a big deal (technicaly I mean, it'll maybe take some time). I'm not a windows dev specialist, I'm maybe missing a point somewhere. > > I would suggest to keep it as a separate sapi for now, or forever if it works. > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >