Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47534
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.185 as permitted sender)
Message-ID: <7.0.1.0.2.20100324003600.13ff3310@zend.com>
Date: Wed, 24 Mar 2010 01:00:34 +0200
To: "Derick Rethans" <derick@php.net>
Cc: "Antony Dovgal" <tony@daylessday.org>,
 "php-dev" <internals@lists.php.net>
In-Reply-To: <alpine.DEB.2.00.1003232222380.4153@kossu.derickrethans.nl>
References: <4BA8EF6F.8010503@daylessday.org>
 <4BA8F72E.5090701@sci.fi>
 <4BA8F985.1090109@daylessday.org>
 <bd9320b31003231226v302da734g391a9eff9494bccf@mail.gmail.com>
 <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>
 <alpine.DEB.2.00.1003232155350.4153@kossu.derickrethans.nl>
 <7.0.1.0.2.20100324000837.13ff3080@zend.com>
 <alpine.DEB.2.00.1003232222380.4153@kossu.derickrethans.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] FPM RFC
From: zeev@zend.com (Zeev Suraski)

At 00:33 24/03/2010, Derick Rethans wrote:

>On Wed, 24 Mar 2010, Zeev Suraski wrote:
>
> > At 00:01 24/03/2010, Derick Rethans wrote:
> > > I don't see how this actually matters. None of the other SAPIs are
> > > configured with a php.ini syntax.
> >
> > None of the other SAPIs are configured, period.
>
>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.

I think it's very different.  Would we include that LUA code in 
PHP?  That's the difference.  It's going to become a part of PHP, 
it's going to be supported by PHP, it should use the same mechanisms 
as the rest of PHP.

>My take on this is:
>
>- Add sapi/fpm to trunk; it's standalone, it works
>- If somebody finds it necessary, write the code for it and we can
>   discuss whether we actually want a .ini file like syntax.

I think there was substantial opposition to keeping the XML-based 
configuration file.  The obvious default was .ini-syntax, and now 
that it's clear it's very much a viable option - I think we should go for it.
I think keeping it as XML and then putting the burden of moving it to 
another format the many people that commented on the RFC - after they 
write the code, no less - is not reasonable.

My take:
- Put it in trunk, subject to change in the configuration file format 
before it gets released.

Principals aside, I can take care of moving it to .ini format.

Zeev