Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69803 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51668 invoked from network); 23 Oct 2013 13:47:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2013 13:47:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.171 mail-we0-f171.google.com Received: from [74.125.82.171] ([74.125.82.171:38378] helo=mail-we0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/2B-10840-A53D7625 for ; Wed, 23 Oct 2013 09:47:07 -0400 Received: by mail-we0-f171.google.com with SMTP id t60so839469wes.30 for ; Wed, 23 Oct 2013 06:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Szezc3FNQuI46JHAxkne479aVE3LcYAh2hppLiv+FLw=; b=hXJig8vQ8ZU/ws2dD2NxmyS4dfo4zrSENLYTlPhwVdRL5cEhIha/arwPvCg826N2nR sk9VmtLb3NMH61YWqihzs8ZGSYRepCnTMSjRLpwzMaj795JuF6ImhNvfQdVwX4rbarzV vieF/yhzWpSg27m6JLu3G69KgtGEJFnjbD84FPC/IXUYfrmcSl8+nEfsuoe5Vir7rj9s 8a2Z9KGAa5sVCCAmW4YycqodWugZ8Ls5koPjKRjcz9lmiEWih8KWdIF5/l911uClZB6Y GhSQZuOYdDHNVnrE8aJM77BYuFAYgxvu+Of5bpiWK3jW6h5SqCYNB21NCW29bFOSjesp W47A== X-Received: by 10.194.143.18 with SMTP id sa18mr1779025wjb.70.1382536023417; Wed, 23 Oct 2013 06:47:03 -0700 (PDT) Received: from [192.168.0.163] ([62.189.198.114]) by mx.google.com with ESMTPSA id ft19sm17183676wic.5.2013.10.23.06.47.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 06:47:03 -0700 (PDT) Message-ID: <5267D356.4040801@gmail.com> Date: Wed, 23 Oct 2013 14:47:02 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: internals@lists.php.net References: <52603390.7020609@ajf.me> <5266E5D0.3090506@ajf.me> <526712D2.7080100@ajf.me> <526717C5.6020509@ajf.me> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PATCH] Add apache_request_headers() and apache_response_headers() to the CLI server From: rowan.collins@gmail.com (Rowan Collins) Yasuo Ohgaki wrote (on 23/10/2013): > It is not good idea introducing non-standard function name in new releases. > getallheaders() should be depreciated in the future as it does not conform > current naming convention. While I would tend to agree that adding more "badly" named functions/aliases would be unfortunate, I would have thought removing the "bad" name would risk opening a rather large can of worms. From the prominently linked blog post on RFCs [https://blogs.oracle.com/opal/entry/the_mysterious_php_rfc_process]: > Don't start an RFC (or mail list discussion) about standardizing PHP > function names and function argument orders. [...] This has been > discussed ad infinitum. Review previous discussions and feel free to > fork PHP on github. IMHO, there would need to be a pretty strong argument for this particular function to be permanently renamed without reopening that discussion for all the other poorly named functions in core. (Note: this is NOT an invitation to reopen that discussion!) Perhaps a better idea (which already came up recently) would be to create a new module for dealing with SAPI I/O (request body data, environment vars, cookies, etc) and include HTTP header handling in that. This could also allow better symmetry for *setting* response headers, to replace header(), in the same way as setcookie()/$_COOKIE. Regards, -- Rowan Collins [IMSoP]