Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47509 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35136 invoked from network); 23 Mar 2010 20:44:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 20:44:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=jerome@loyet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jerome@loyet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain loyet.net from 74.125.82.170 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 74.125.82.170 mail-wy0-f170.google.com Received: from [74.125.82.170] ([74.125.82.170:46697] helo=mail-wy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A1/3C-03444-C3829AB4 for ; Tue, 23 Mar 2010 15:44:45 -0500 Received: by wyb36 with SMTP id 36so3424615wyb.29 for ; Tue, 23 Mar 2010 13:44:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.86.193 with SMTP id w43mr3884059wee.16.1269377081132; Tue, 23 Mar 2010 13:44:41 -0700 (PDT) In-Reply-To: <7.0.1.0.2.20100323222839.12d7b088@zend.com> References: <4BA8EF6F.8010503@daylessday.org> <4BA8F72E.5090701@sci.fi> <4BA8F985.1090109@daylessday.org> <4BA919D2.3060605@daylessday.org> <7.0.1.0.2.20100323222839.12d7b088@zend.com> Date: Tue, 23 Mar 2010 21:44:41 +0100 Message-ID: <3bea96c41003231344l20e6c64ewad7715bebc2f773f@mail.gmail.com> To: Zeev Suraski Cc: Antony Dovgal , Michael Shadle , php-dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] FPM RFC From: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) 2010/3/23 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. =A0In fact I think it was very clear that using ph= p.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. =A0.ini is also easier than XML for mere mor= tals. In fact with INI syntax, there is a serious missing cause there is no include system shiped with. And with FPM as there is potentialy many "vhosts", it's necessary to have an include system to feet all system administrator needs. > > Zeev > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >