Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47988 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38200 invoked from network); 15 Apr 2010 17:28:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2010 17:28:16 -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 209.85.218.219 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 209.85.218.219 mail-bw0-f219.google.com Received: from [209.85.218.219] ([209.85.218.219:50470] helo=mail-bw0-f219.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/49-22079-EAC47CB4 for ; Thu, 15 Apr 2010 13:28:16 -0400 Received: by bwz19 with SMTP id 19so16275bwz.1 for ; Thu, 15 Apr 2010 10:28:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.135.83 with HTTP; Thu, 15 Apr 2010 10:28:10 -0700 (PDT) In-Reply-To: <4BC74ACA.8030302@oracle.com> References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com> <4BC4B553.3020807@oracle.com> <4BC4BBF9.4000903@oracle.com> <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> <4BC74ACA.8030302@oracle.com> Date: Thu, 15 Apr 2010 19:28:10 +0200 Received: by 10.239.173.206 with SMTP id g14mr44557hbf.67.1271352490441; Thu, 15 Apr 2010 10:28:10 -0700 (PDT) Message-ID: To: Christopher Jones Cc: internals@lists.php.net 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?=) 2010/4/15 Christopher Jones : > > > On 04/13/2010 12:01 PM, Zeev Suraski wrote: >> >> 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 layer below it. Implementing include() can be done at >> either layer. If it's implemented at the bottom layer (ZE) then it'll >> transparently effect any and all .ini's - not sure we want that (maybe). >> If 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-code layer). >> >> Zeev >> > > Thanks Zeev. =A0J=E9r=F4me should add this clarification to the RFC. > already done. ++ jerome