Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47925 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60779 invoked from network); 13 Apr 2010 19:34:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2010 19:34:12 -0000 Authentication-Results: pb1.pair.com header.from=jerome@loyet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jerome@loyet.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain loyet.net from 74.125.83.170 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 74.125.83.170 mail-pv0-f170.google.com Received: from [74.125.83.170] ([74.125.83.170:58336] helo=mail-pv0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/5E-32795-337C4CB4 for ; Tue, 13 Apr 2010 15:34:11 -0400 Received: by pvg6 with SMTP id 6so4219823pvg.29 for ; Tue, 13 Apr 2010 12:34:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.216.7 with HTTP; Tue, 13 Apr 2010 12:34:08 -0700 (PDT) In-Reply-To: <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com> <4BC4B553.3020807@oracle.com> <4BC4BBF9.4000903@oracle.com> <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> Date: Tue, 13 Apr 2010 21:34:08 +0200 Received: by 10.142.60.18 with SMTP id i18mr3055774wfa.275.1271187248472; Tue, 13 Apr 2010 12:34:08 -0700 (PDT) Message-ID: To: Zeev Suraski Cc: Christopher Jones , php-dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] FPM INI syntax From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) Le 13 avril 2010 21:01, Zeev Suraski a =E9crit : > At 21:46 13/04/2010, Christopher Jones wrote: > > >> J=E9r=F4me Loyet wrote: >>> >>> Le 13 avril 2010 20:17, Christopher Jones >>> a =E9crit : >>>> >>>> J=E9r=F4me Loyet wrote: >>>>> >>>>> Hi guys, >>>>> >>>>> 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. >>>>> >>>>> ++ Jerome >>>> >>>> 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 lay= er > below it. =A0Implementing include() can be done at either layer. =A0If it= 's > implemented at the bottom layer (ZE) then it'll transparently effect any = and > all .ini's - not sure we want that (maybe). =A0If we implement it at the = top > layer - the custom code that's responsible for fpm.ini, then it will be > entirely specific to it and won't effect php.ini behavior in any way > (exactly like the support for the 'extension' keyword is implemented for > php.ini, but not for any other .ini's - because it's at the top custom-co= de > layer). > Thanks Zeev for translating my thought :)