Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57254 invoked from network); 11 Feb 2009 14:59:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2009 14:59:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.220.18 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@googlemail.com X-Host-Fingerprint: 209.85.220.18 mail-fx0-f18.google.com Received: from [209.85.220.18] ([209.85.220.18:39931] helo=mail-fx0-f18.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/19-12172-3D7E2994 for ; Wed, 11 Feb 2009 09:59:32 -0500 Received: by fxm11 with SMTP id 11so212867fxm.23 for ; Wed, 11 Feb 2009 06:59:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=I5f4kuA+gYKGoBouZ5VV25hApCoa4vRDKiu5Nswd42Y=; b=OSE2WLIv7QJLTuH2rPFgErwIZg8SczGvGnGIS+u9INV9NrlCuCSqlkXeQay+me/DiB FjLHpYcR44Bh3z1M6lI57zAq+u9YDiiXt1t3IArcD5TxNKm02hHumPu5u4uisHuPIz3e NH8v/npPTWw+mYD6QVqDLXMRHcGJlDkhJ7hMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=ECTJLFsTyb6V5lhECs4ZxQQi0FyKG+0yVKWdqMcnvA9IPBwJ7jAAHIWEY4q8psABEc Xvv3XsbBHDQAIEX96S5jw3MozJkxlAyiUm8ciL28OAeqxtQVdS9s7yI96fWONpR7Ilew STVeGEcwzIU920o/gcpxOeGeksXWSqOb/ZoFY= MIME-Version: 1.0 Received: by 10.223.113.9 with SMTP id y9mr4704666fap.61.1234364249125; Wed, 11 Feb 2009 06:57:29 -0800 (PST) Reply-To: RQuadling@googlemail.com In-Reply-To: References: <4992E00A.9010209@cschneid.com> Date: Wed, 11 Feb 2009 14:57:28 +0000 Message-ID: <10845a340902110657l36d3489exb9085fa92a9b2245@mail.gmail.com> To: Ilia Alshanetsky Cc: Christian Schneider , Eric Stewart , internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: RFC for new INI's From: rquadling@googlemail.com (Richard Quadling) 2009/2/11 Ilia Alshanetsky : > > On 11-Feb-09, at 9:26 AM, Christian Schneider wrote: > >> Eric Stewart wrote: >>> >>> A new RFC for PHP's proposed INI files have been added to the wiki. Below >>> is >>> a direct link to the page. >>> http://wiki.php.net/rfc/newinis >> >> Good work IMHO. >> >> Similar to what Karsten Dambekalns wrote I think we should only have a >> difference between devel and production for display/logging options, but >> not for options changing the 'behaviour' of PHP. >> >> So I'd propose >> allow_call_time_pass_reference = Off (devel) / On (production) >> display_errors = On (devel) / Off (production) >> display_startup_errors = On (devel) / Off (production) >> html_errors = On (devel) / Off (production) >> session.bug_compat_warn = On (devel) / Off (production) >> track_errors = On (devel) / Off (production) >> >> but >> output_buffering = 4096 ; Changes header()/compression filter behaviour > > I think it makes sense to have it on in both. > >> register_argc_argv = Off ; Why should devel have access if prod doesn't? > > off in both. > >> request_order = GPCS ; Why should devel/production differ? >> session.bug_compat_42 = Off ; Why should devel/production differ? >> > > Agreed. > > Ilia Alshanetsky > > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > One of the things about the 2 files is the amount of consistency between them. The differences are scattered throughout the file. Considering that these are our recommendations, would it not be possible to have the differences at the top of the file and the consistent ones below that. [PHP] ; Here are the PHP's group recommended settings for development foo=bar ; Now the rest of the settings which the PHP group have no explicit opinion on. and [PHP] ; Here are the PHP's group recommended settings for a production environment foo=baz ; Now the rest of the settings which the PHP group have no explicit opinion on. This way, the top few lines clearly indicate the areas where the PHP group feel there should be distinct differences between a production environment and a development environment. This is how I've structured my ini files (for example, CLI has no HTML highlighting output, whereas CGI/ISAPI does - just an example difference). The rest of the settings are consistent between all the SAPIs, so I have them further down the files. Regards, Richard. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"