Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47973 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66897 invoked from network); 15 Apr 2010 11:21:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2010 11:21:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; 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:49698] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/4E-20494-2A6F6CB4 for ; Thu, 15 Apr 2010 07:21:07 -0400 Received: from il-gw1.zend.com (unknown [10.1.1.21]) by il-mr1.zend.com (Postfix) with ESMTP id 1AE7E504C6 for ; Thu, 15 Apr 2010 14:00:12 +0300 (IDT) Received: from LAP-ZEEV.zend.com ([10.1.2.50]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Apr 2010 14:21:03 +0300 Message-ID: <7.0.1.0.2.20100415141933.0e2a53d8@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Thu, 15 Apr 2010 14:21:03 +0300 To: internals@lists.php.net In-Reply-To: <7.0.1.0.2.20100415140350.0e2a5290@zend.com> References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com> <4BC4B553.3020807@oracle.com> <4BC4BBF9.4000903@oracle.com> <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> <7.0.1.0.2.20100415140350.0e2a5290@zend.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 15 Apr 2010 11:21:03.0762 (UTC) FILETIME=[BC173F20:01CADC8D] Subject: Re: [PHP-DEV] [RFC] FPM INI syntax From: zeev@zend.com (Zeev Suraski) BTW - I think the include discussion is very much=20 secondary here. I'm not sure why we really need=20 include for this particular config file, and it=20 may make sense to separate these two things=20 altogether - moving to fpm.ini, and whether or=20 not we want .ini files to support include. Zeev At 14:11 15/04/2010, Zeev Suraski wrote: >At 13:56 15/04/2010, Derick Rethans wrote: >>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=97not only with include,, but >>section headers are totally ignored in php.ini as well. > >Derick, > >You're confusing syntax and semantics. >The syntax is very much .ini, it's identical to php.ini's syntax. >The semantics is designed to fit the needs of=20 >FPM. If you follow my emails on this topic=20 >you'd see that this is what I was pushing all along, nothing new here. >It's much like the syntax of the current config=20 >file is XML - but we could implement the semantics in dozens of different= ways. > >> 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 completely disagree. > >Zeev > >-- >PHP Internals - PHP Runtime Development Mailing List >To unsubscribe, visit: http://www.php.net/unsub.php