Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47923 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51045 invoked from network); 13 Apr 2010 19:07:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2010 19:07:32 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.185 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 212.25.124.185 il-mr1.zend.com Received: from [212.25.124.185] ([212.25.124.185:59211] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/8C-32795-1F0C4CB4 for ; Tue, 13 Apr 2010 15:07:31 -0400 Received: from il-gw1.zend.com (unknown [10.1.1.21]) by il-mr1.zend.com (Postfix) with ESMTP id 1F68350515; Tue, 13 Apr 2010 21:46:40 +0300 (IDT) Received: from LAP-ZEEV.zend.com ([10.1.20.51]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Apr 2010 22:07:26 +0300 Message-ID: <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 13 Apr 2010 22:01:21 +0300 To: Christopher Jones Cc: =?iso-8859-1?Q?J=E9r=F4me?= Loyet , php-dev In-Reply-To: <4BC4BBF9.4000903@oracle.com> References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com> <4BC4B553.3020807@oracle.com> <4BC4BBF9.4000903@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 13 Apr 2010 19:07:26.0145 (UTC) FILETIME=[8E108B10:01CADB3C] Subject: Re: [PHP-DEV] [RFC] FPM INI syntax From: zeev@zend.com (Zeev Suraski) 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=20 custom code responsible for parsing fpm.ini, and=20 not in the ZE .ini parser which would be the=20 layer below it. Implementing include() can be=20 done at either layer. If it's implemented at the=20 bottom layer (ZE) then it'll transparently effect=20 any and all .ini's - not sure we want that=20 (maybe). If we implement it at the top layer -=20 the custom code that's responsible for fpm.ini,=20 then it will be entirely specific to it and won't=20 effect php.ini behavior in any way (exactly like=20 the support for the 'extension' keyword is=20 implemented for php.ini, but not for any other=20 .ini's - because it's at the top custom-code layer). Zeev=20