Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.191 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:content-transfer-encoding;
        b=EnvZDKLv6lti8lQLUBii3Mnd3aMPBhP7UO8tRTVGPF7W2PkohWMVKH2Vi94A40vCKV
         zn7VMQSvervqzueXl9OlU+l/6GtLzsktpYZGlJq2sd6qnBJwbcdcled/pLcKOGHaiOdT
         YtRYa2t/mwBGaQ6MjnIIYdLbPgoCN5NypwIds=
MIME-Version: 1.0
In-Reply-To: <3bea96c41003250709jd391239te35ab88b46e4803e@mail.gmail.com>
References: <4BA8EF6F.8010503@daylessday.org> <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>
	 <4BA9CB98.6080102@daylessday.org>
	 <7.0.1.0.2.20100324102437.0b491a68@zend.com>
	 <4BA9D167.30006@daylessday.org>
	 <99cf22521003240334y6fb76fbcs4347429f3be48d49@mail.gmail.com>
	 <3bea96c41003250709jd391239te35ab88b46e4803e@mail.gmail.com>
Date: Thu, 25 Mar 2010 11:30:24 -0700
Message-ID: <bd9320b31003251130g59217bcejec5abe0125ccdab9@mail.gmail.com>
To: =?UTF-8?B?SsOpcsO0bWUgTG95ZXQ=?= <jerome@loyet.net>
Cc: dreamcat four <dreamcat4@gmail.com>, Antony Dovgal <tony@daylessday.org>, 
	Zeev Suraski <zeev@zend.com>, Derick Rethans <derick@php.net>, 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: mike503@gmail.com (Michael Shadle)

2010/3/25 J=C3=A9r=C3=B4me Loyet <jerome@loyet.net>:

> ** Default Section **
> Talking about redundancy. When there is more than one pool, there is
> several parameters which remain the same. Why should we type them
> several time ? The idea is to define a special pool, which will not be
> started but only be used as a "template" with default values for other
> pools. Common parameters will be set in the default pool and in each
> pool only specifics parameters will be set. here some example in the
> two previous cases

Redundancy can be addressed by includes.

I was thinking of creating an RFC for php.ini file support of
includes, but FPM should support includes either - whether it is it's
own INI file, the same XML file it's always been, whatever.

It should be added to the FPM RFC.