Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70549 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29377 invoked from network); 9 Dec 2013 14:17:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2013 14:17:14 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.176 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.176 mail-qc0-f176.google.com Received: from [209.85.216.176] ([209.85.216.176:63155] helo=mail-qc0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/00-28714-8E0D5A25 for ; Mon, 09 Dec 2013 09:17:12 -0500 Received: by mail-qc0-f176.google.com with SMTP id i8so2704155qcq.7 for ; Mon, 09 Dec 2013 06:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ba47j74hPrh8yVyLKLClWo7G+u3dvsXRqoJ/jZZP9i8=; b=Ngwk8W7L8vfVcQi32gtTIX4cLxjEC95VeBuHpZOEIjJSKiWrX6+iciiUsk87mQejDu G+3YH4HbXKbTHijEnvUTnLKGtNpaW8evfZLNg5WIVGP36hM7o2ybMRFslRlE8YkDyg9f OIzGwSDbko3JeaeUi8AcxVSrvsfi5eN/mtU0/4cGtfaKEOVuujO1+QjJHd3nv0lgaNkT NQx1ECXav3T4Ok25YBuJpUZmfHf7fc6kwkXCmKOCouGTy+do45CikRceKhdI2USekn4S GKyniQTWIe9yRahEjmkw5SL48Q5wsUChdbVKiBE6cHZjx9ABEO1SPcF/17h4K7M+uCm3 MIGw== MIME-Version: 1.0 X-Received: by 10.229.126.9 with SMTP id a9mr33104204qcs.0.1386598629231; Mon, 09 Dec 2013 06:17:09 -0800 (PST) Received: by 10.140.37.179 with HTTP; Mon, 9 Dec 2013 06:17:09 -0800 (PST) In-Reply-To: References: <5293E54F.9060604@rotorised.com> <1385628146.16543.0.camel@smugmug> <1385969508.2637.3.camel@smugmug> Date: Mon, 9 Dec 2013 15:17:09 +0100 Message-ID: To: Mike Cc: Julien Pauli , Adam Harvey , Yasuo Ohgaki , "internals@lists.php.net" , Michael Wallner , Ryan McCue Content-Type: multipart/alternative; boundary=001a1133d6eebdf08704ed1aa6c0 Subject: Re: [PHP-DEV] Re: [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA) From: tyra3l@gmail.com (Ferenc Kovacs) --001a1133d6eebdf08704ed1aa6c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Dec 7, 2013 at 8:39 AM, Ferenc Kovacs wrote: > >> >>> > I think it would make sense, to have an RFC for 5.6 about introducing >>> > the new stream, the new ini option and and how does it keeps userland >>> > BC while providing a way to opt-in for the performance gain, and that >>> > it introduces an E_DEPRECATED so we can remove the ini and the raw >>> > post global variable in the next major version. >>> >>> I think we cannot add E_DEPRECATED to the INI-setting unless we make it= s >>> default -1... which breaks BC :p >>> >>> Also, I think two RFCs would be quite much, but I already gave up my >>> renitency. >>> >> >> we could emmit the error from populate_raw_post_data in >> main/php_content_types.c, telling people that the auto population of >> $HTTP_RAW_POST_DATA along with the use of always_populate_raw_post_data >> will go away, and they should set always_populate_raw_post_data to -1 an= d >> populate that variable for themself if their want to be forward compatib= le >> (and silence the E_DEPRECATED messages). >> >> >> > Hi, > > Any update on this? > I would be ok to merge with the PR in the current form, as it resolves th= e > BC issue, but if we want to remove the INI setting in the future, then > adding the E_DEPRECATED would be important step. > > -- > Ferenc Kov=C3=A1cs > @Tyr43l - http://tyrael.hu > bump. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a1133d6eebdf08704ed1aa6c0--