Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47924 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53547 invoked from network); 13 Apr 2010 19:10:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2010 19:10:25 -0000 Authentication-Results: pb1.pair.com header.from=mike503@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=mike503@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: mike503@gmail.com X-Host-Fingerprint: 209.85.160.42 mail-pw0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:47414] helo=mail-pw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 48/0D-32795-1A1C4CB4 for ; Tue, 13 Apr 2010 15:10:25 -0400 Received: by pwi8 with SMTP id 8so5866305pwi.29 for ; Tue, 13 Apr 2010 12:10:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=D+kvBtdc1nvPjX/R3tnYlNXeN0nCpm1xmLkRaK8BrzI=; b=EMmzbEu0rpWELbaJytP2UAW5SvwWImIvSd0Bw8osmg/t7xSrsqv8ssqOKBH8bZJFJN yyIawoErpWn6zOqrXpplONvpqcigVf0ZDLCgL2fgzMbeQxXb9cccDpZp967oRQvT04Q0 oocgpWupTYEZdv2PcrAoZPPDgB+4VSHAagLy0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RnWOgRvsJ8ABUe3X2IQmD/cgOrliMqRokrCR4lgFbhEdAJy8IuzZZ57OU1HF5q2PNs Ewg66wtVqPsxUI/gzVME9MwEwj3oHsbuEiB94Q2HIOECevUGVy2L11PXoqGjDgulbjPt slrGezHJI4EaLSRmdxoYqugi/y8WNLcdLvrtE= MIME-Version: 1.0 Received: by 10.231.54.199 with HTTP; Tue, 13 Apr 2010 12:10:22 -0700 (PDT) In-Reply-To: <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> References: <3bea96c41003301008va8ea1cbif8c16be11451eaf8@mail.gmail.com> <4BC4B553.3020807@oracle.com> <4BC4BBF9.4000903@oracle.com> <7.0.1.0.2.20100413215139.0dbcfdd8@zend.com> Date: Tue, 13 Apr 2010 12:10:22 -0700 Received: by 10.114.33.26 with SMTP id g26mr5968560wag.216.1271185822224; Tue, 13 Apr 2010 12:10:22 -0700 (PDT) Message-ID: To: Zeev Suraski Cc: Christopher Jones , =?UTF-8?B?SsOpcsO0bWUgTG95ZXQ=?= , php-dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] FPM INI syntax From: mike503@gmail.com (Michael Shadle) 2010/4/13 Zeev Suraski : > 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 lay= er > below it. =C2=A0Implementing include() can be done at either layer. =C2= =A0If it's > implemented at the bottom layer (ZE) then it'll transparently effect any = and > all .ini's - not sure we want that (maybe). =C2=A0If we implement it at t= he 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-co= de > layer). I think generic include capability for php .ini files would be quite handy.