Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46363
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
Date: Wed, 9 Dec 2009 15:55:48 +0100
Message-ID: <3bea96c40912090655i263115bbid923deb2bdf296a6@mail.gmail.com>
To: php-dev <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [PHP-FPM] syntax of configuration file
From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=)

Hi guys,

I start a new thread about the syntax that should be used in php-fpm
to replace xml.

As discussed before, there is different point on view on this subject:
- INI to stay in the PHP philosophy / practicals
- nginx because it was the will of the original authors

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 ?

It's possible to imagine a default syntax: INI. and let the user to
choose another one. There is many ways to do so:
- Add a prefix to the file choose from command line:
php-fpm -y ngx:/etc/php-fpm.conf
php-fpm -y nginx:/etc/php-fpm.conf
php-fpm -y ini:/etc/php-fpm.conf
php-fpm -y yaml:/etc/php-fpm.conf
...
- a Shebang in all configuration file (if none it's considered as ini)
#!ini
#!nginx
#!ngx
#!yaml

- autodetection

I think this could be a good idea which will, I hope, satisfy us all.
Moreoever, this could be easly extended from futures end-user needs.

I've already started (and almost finished) to hack php-fpm to move
from xml to nginx. I can and want make this work. But we have to meet
a general approval here.

Hope this help.

++ jerome