Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47970
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.219 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:date:message-id:subject:from:to
         :cc:content-type;
        b=Nl1TDLzITgu5K++2qPDtes6CwKd7JsP7koOdnBk3hlAFyV7PrMB94q08pkwSKsUXQS
         F/Qp/FSYn8cpIYejgz1N+4F6PFpWRtJdNpTkYe9INxpvX8lRLzkiKyAlbW9Zz/n86zaz
         o36yZ9N8ZkNGv7gVD0KdK3xwR8ZYLD8yRE0h8=
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1004151152450.8571@kossu.derickrethans.nl>
References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com>
	 <4BC4B553.3020807@oracle.com>
	 <o2g3bea96c41004131142u282c1727w1725f03e9fa670c4@mail.gmail.com>
	 <4BC4BBF9.4000903@oracle.com>
	 <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com>
	 <alpine.DEB.2.00.1004151152450.8571@kossu.derickrethans.nl>
Date: Thu, 15 Apr 2010 13:12:03 +0200
Message-ID: <y2ib54d0abe1004150412l176b6c7drba731c843c4d8b83@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Zeev Suraski <zeev@zend.com>, Christopher Jones <christopher.jones@oracle.com>, 
	=?UTF-8?B?SsOpcsO0bWUgTG95ZXQ=?= <jerome@loyet.net>, 
	php-dev <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0015175cd2f679339004844490d7
Subject: Re: [PHP-DEV] [RFC] FPM INI syntax
From: tyra3l@gmail.com (Ferenc Kovacs)

--0015175cd2f679339004844490d7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2010/4/15 Derick Rethans <derick@php.net>

> On Tue, 13 Apr 2010, Zeev Suraski wrote:
>
> > At 21:46 13/04/2010, Christopher Jones wrote:
> >
> > > J=C3=A9r=C3=B4me Loyet wrote:
> > > > Le 13 avril 2010 20:17, Christopher Jones
> > > > <christopher.jones@oracle.com> a =C3=A9crit :
> > > > >
> > > > > J=C3=A9r=C3=B4me Loyet wrote:
> > > > > >
> > > > > > As dreamcast4 advises me in the previous FPM conversation, I
> > > > > > just wrote the RFC for the FPM INI syntax.
> > > > > >
> > > > > > It can be read here: http://wiki.php.net/rfc/fpm/ini_syntax
> > > > > >
> > > > > > Tell me what you think.
> > > > > >
> > > > > I think the RFC should clearly state what is new generic php.ini
> > > > > functionality (e.g. include) and what is specific for FPM.
> > > >
> > > > for me everything is specific to FPM
> > >
> > > How is "include" specific to FPM?
> >
> > What he means is that it'll be implemented in the custom code
> > responsible for parsing fpm.ini, and not in the ZE .ini parser which
> > would be the layer below it.
>
> Uh, so what you're saying is that you want to use INI syntax for FPM so
> that it is inline with php's INI sytanx, but then modify it with extra
> statements so that it isn't the same anymore=E2=80=94not only with includ=
e, but
> section headers are totally ignored in php.ini as well. This whole new
> INI thing is making less and less sense. The XML format like we have now
> is much easier, self documented, doesn't create two different ini
> formats and generally just works well. I'd be a big -1 on this special
> FPM-specific INI syntax.
>
> Derick
>
>
Agree, I thought that the include part will be handled from the application=
.
I mean you parse the global config, read the include param, and read each o=
f
the matching ini for merging them to the original config format.

Tyrael

--0015175cd2f679339004844490d7--