Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47532 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80615 invoked from network); 23 Mar 2010 22:41:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 22:41:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-ww0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:48567] helo=mail-ww0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B3/70-12746-C9349AB4 for ; Tue, 23 Mar 2010 17:41:33 -0500 Received: by wwc33 with SMTP id 33so257074wwc.29 for ; Tue, 23 Mar 2010 15:41:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=K5Rh31/ZB1/UsKBHpRBieKGLo1DXPGJPYJ/kUhozx58=; b=atPEVCzv8rI2SoN6jwx1/Z/64fV5DS+z45hjD8zqqblBzF11u2KS1IjAfUHs8SlMOB b0sZW8nH3r74ET3VyfVpe6epK+y8VS4KhllBbE15MRIwNB/gbvXHVUx7sI+9rfRJkSGS paV3v/qiusyOUhN8TNGgvllg/7A6GU3W/uy/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=O/S/TigxFhwhh7yPDPFJX7nE7oPUfg2oQ9Gn3lwiHoixSJpS9oEhLt2eCWR5EGlQ1X h0pZT4X68Vp3KFYChvA6u27F7WW1BeUPb50nfjIxf1ZKpvbGGvkaRJee+xH40jPLISm7 UrxR4uJA615QcTRjg9YnSMq5vEaWzvmYzpfgs= MIME-Version: 1.0 Received: by 10.216.87.12 with SMTP id x12mr1037954wee.185.1269384087112; Tue, 23 Mar 2010 15:41:27 -0700 (PDT) In-Reply-To: References: <4BA8EF6F.8010503@daylessday.org> <4BA919D2.3060605@daylessday.org> <7.0.1.0.2.20100323222839.12d7b088@zend.com> <3bea96c41003231344l20e6c64ewad7715bebc2f773f@mail.gmail.com> <7.0.1.0.2.20100323225305.12e71c38@zend.com> <4BA92B72.1050207@daylessday.org> <7.0.1.0.2.20100323230046.12e71d80@zend.com> <7.0.1.0.2.20100324000837.13ff3080@zend.com> Date: Tue, 23 Mar 2010 23:41:27 +0100 Message-ID: To: Derick Rethans Cc: Zeev Suraski , Antony Dovgal , php-dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] FPM RFC From: pierre.php@gmail.com (Pierre Joye) On Tue, Mar 23, 2010 at 11:33 PM, Derick Rethans wrote: > That's not true. You configure the fastcgi SAPI for lighttpd in the > lighttpd config, in LUA. Sure, it's the web-server side of it, but it's > no different from sapi/fpm which is its own little wrapper instead of > the one that comes with lighttpd. > > ## Start an FastCGI server for php > fastcgi.server =A0 =A0=3D ( ".php" =3D> > =A0 =A0 =A0 =A0"bin-copy-environment" =3D> ( > =A0 =A0 =A0 =A0 =A0 =A0"PATH", "SHELL", "USER" > =A0 =A0 =A0 =A0), > =A0 =A0 =A0 =A0"broken-scriptfilename" =3D> "enable" > =A0 =A0)) > ) > > This is in no way different than doing the configuration for the FPM > sapi in their XML file. That's not true either. That's clearly a server configuration and has absolutely nothing to do with PHP. It is a FastCGI configuration (in this case for lighttpd) and it will work the same for any other FastCGI (environment settings may differ but the way to do it does not). It is slightly different with mod_php as php actually extends the configuration syntax of Apache. But that's pretty much the same than with fastcgi. What I would suggest is to get it into trunk soon so we can test it more easily. About the configuration format, it seems to me that we should figure out a way to do it in php.ini for consistency. But for my own sanity, please don't bring XML to the game. If a more flexible format is required, please consider YAML. However, is it not possible to extend our ini parser to support what we need for FPM (did not check all the details)? Cheers, --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org