Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46369
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain loyet.net from 209.85.223.195 cause and error)
MIME-Version: 1.0
In-Reply-To: <fe05d1540912090816v77aadff6k1be1dea5af25942c@mail.gmail.com>
References: <3bea96c40912090655i263115bbid923deb2bdf296a6@mail.gmail.com>
	 <4B1FBAF0.7020506@daylessday.org>
	 <3bea96c40912090711o3927e257gab87783a6763f172@mail.gmail.com>
	 <fe05d1540912090816v77aadff6k1be1dea5af25942c@mail.gmail.com>
Date: Wed, 9 Dec 2009 18:44:40 +0100
Message-ID: <3bea96c40912090944r23831b52pc57dae2b7905c15@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Antony Dovgal <tony@daylessday.org>, php-dev <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [PHP-FPM] syntax of configuration file
From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=)

Le 9 d=E9cembre 2009 17:16, Pierre Joye <pierre.php@gmail.com> a =E9crit :
> hi,
>
> 2009/12/9 J=E9r=F4me Loyet <jerome@loyet.net>:
>
>>>> We already discussed pros/cons of the two solutions. But why don't we
>>>> allow several syntaxes ? And let the end user to choose the better one
>>>> for its need ?
>>>
>>> No. Thank you.
>>> EOD
>>>
>>
>> and why of that ? Why is it already EOD wihtout arguing ? php-fpm just
>> started in PHP core and there is willing from people to help and make
>> php-fpm better, which I tought was the final goal.
>
> It is, however I have to agree with Tony here, adding a fpm specific
> syntax makes little sense. Or do you have any killing arguments for
> this new syntax (like not possible to do it otherwise, stoping point
> etc.)?
>

I don't have killing arguments I just came with a discussion which
seems fair here. Now it's xml and before it's been integrated there
were discutions about changing it to nginx. So I bring back the
discution here.

about multiple syntax it was a proposal which was about to make all
users happy but the complexity and the confusion is a good argument, I
heard it.

So let have the question another way:
Do we keep XML or do we switch to something else ? If so, which format ?

I and some others think xml is not appropriate here because of the
complexity. So I do think there is a need to change.

INI or other ?
INI is used widely in PHP and users know it. But it's not well adapted
for the actual php-fpm configuration organisation. (properties in
sections or subsections). If choosed how will it be organized ?

If we want something else than XML and INI, we can use ngxin like or
yaml configuration file, or other ...

We have to decide to go forward here.

++ Jerome