Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47529
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.209 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=WrirQb0clZ58oGzH0Y6dVJ01By9x+PhLf2YgpOhBo0ICHj5gwgZbw4VzIzB2G1aqBu
         NODh31QgoRWAQSh5JTkE28JMvnXaEhPx5Abl9N1h6EV3GA8nunjDWa+sFfaQbwhNmigK
         wQq/0y5pRATjJ9+q/Z21NuHNIiRS3uLdaxM6g=
MIME-Version: 1.0
In-Reply-To: <7.0.1.0.2.20100324000837.13ff3080@zend.com>
References: <4BA8EF6F.8010503@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>
Date: Tue, 23 Mar 2010 22:35:30 +0000
Message-ID: <99cf22521003231535r3be0089x689ed6f0e0137b61@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Derick Rethans <derick@php.net>, Antony Dovgal <tony@daylessday.org>, 
	php-dev <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] FPM RFC
From: dreamcat4@gmail.com (dreamcat four)

On Tue, Mar 23, 2010 at 10:16 PM, Zeev Suraski <zeev@zend.com> 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; =C2=A0The little configur=
ation
> they do have is done using php.ini.
> This SAPI requires much more configuration - and I agree it's equivalent =
to
> web server configuration - but given that it's going to be bundled in PHP=
,
> it should use the same syntax.

Maybe its valid to make an exception for FPM, given that it has an
exceptional number of configuration options. I would ask, how easy is
PHP.ini to debug? One great thing about the nginx configuration parser
is that it gives decent error messages when you've got the config all
wrong.

But in any case I dont believe you should require Antony to implement
this if its out of his area of expertise, and there are plenty of
other people around who can contribute the code better / more
enthusiastically.

>> =C2=A0That includes IIS, Apache, Lighttpd
>> and others. This is more of a webserver thing than a "PHP thing" so I
>> don't see how it is relevant to require php.ini syntax if this XML
>> configure file works just fine already. I mean, it'd be *nice* to have a
>> non-XML syntax, but for me this is definitely not a requirement for FPM
>> to be added to trunk. If you (or somebody else) wants a php.ini syntax
>> for it, a patch can be written. It's Open Source after all.
>
> For me it is a requirement before the code makes it into a released versi=
on
> of PHP, and I think many others think that way if past discussions are an=
y
> indication. =C2=A0That's what RFCs are for - if people can just go ahead =
and
> implement their original thoughts without paying attention to feedback, w=
hy
> bother?
> Personally I think that the person pushing the code should be responsible
> for implementing the feedback to the RFC (or getting others to do it).
>
> Zeev
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>