Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47508 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32096 invoked from network); 23 Mar 2010 20:31:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 20:31:15 -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:47086] helo=il-mr1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D6/CB-03444-11529AB4 for ; Tue, 23 Mar 2010 15:31:14 -0500 Received: from il-gw1.zend.com (unknown [10.1.1.21]) by il-mr1.zend.com (Postfix) with ESMTP id E678B50510; Tue, 23 Mar 2010 22:11:31 +0200 (IST) Received: from LAP-ZEEV.zend.com ([10.1.20.44]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Mar 2010 22:31:10 +0200 Message-ID: <7.0.1.0.2.20100323222839.12d7b088@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 23 Mar 2010 22:31:09 +0200 To: "Antony Dovgal" Cc: "Michael Shadle" ,"php-dev" In-Reply-To: <4BA919D2.3060605@daylessday.org> References: <4BA8EF6F.8010503@daylessday.org> <4BA8F72E.5090701@sci.fi> <4BA8F985.1090109@daylessday.org> <4BA919D2.3060605@daylessday.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-OriginalArrivalTime: 23 Mar 2010 20:31:10.0409 (UTC) FILETIME=[C615A390:01CACAC7] Subject: Re: [PHP-DEV] FPM RFC From: zeev@zend.com (Zeev Suraski) At 21:43 23/03/2010, Antony Dovgal wrote: > > - The config file change, moving from the XML-based php-fpm.conf to > > using php.ini (I think some work had started on this, but syntax was > > under debate?) > >We've discussed this many times and I thought it's pretty clear that php.ini >syntax won't fit in this situation - the requirements are completely >different. It's not clear at all. In fact I think it was very clear that using php.ini syntax (together with sections if necessary) is very much an option, and I think mostly everyone here leaned towards it. > > - this will make it easier to adopt > >I don't see how. By using syntax we're using everywhere else for configuration, instead of introducing a brand new one. .ini is also easier than XML for mere mortals. Zeev