Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70201
Return-Path: <tyra3l@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 11350 invoked from network); 19 Nov 2013 11:06:18 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Nov 2013 11:06:18 -0000
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.43 as permitted sender)
X-PHP-List-Original-Sender: tyra3l@gmail.com
X-Host-Fingerprint: 209.85.128.43 mail-qe0-f43.google.com  
Received: from [209.85.128.43] ([209.85.128.43:51285] helo=mail-qe0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F8/B2-22480-7264B825 for <internals@lists.php.net>; Tue, 19 Nov 2013 06:06:16 -0500
Received: by mail-qe0-f43.google.com with SMTP id 2so2715061qeb.30
        for <internals@lists.php.net>; Tue, 19 Nov 2013 03:06:13 -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=OnCrUcNB9RBdME83sLWx0EU7jQBTeG2/thXmIRMgjAg=;
        b=P7KGHyfOBBu6m8RBb43JA4aTr+BmH+N/H9ickwtvU2NzebuPg3g0nX9Zy+okV1W+f2
         dYxdRxU7JgI1tLM7fGv8KT15rxGjOKrvkMsrj24WEGCx/dcjM8xsi8fTrwZUvRbaunDW
         Vq3yXvHLdl1i9je9cb8PfEBu0UVkFBDuhLMzF1egHuhvhjbFKM4gns7IHFiMbUqDB68y
         h0pZkfT7kRXWzI3Fv/vHa34CQo/upV6Dvu/jklvumxXVgBWt52OMdmXAUUKbf4xFQSch
         pVY8Tnj4c+6bFr652u5UhgB1H3TE0RQszXOtZTZ8XTS88OFrll25yuf4UvCAU8/YIo/u
         hwfg==
MIME-Version: 1.0
X-Received: by 10.49.104.5 with SMTP id ga5mr42357134qeb.58.1384859173261;
 Tue, 19 Nov 2013 03:06:13 -0800 (PST)
Received: by 10.140.37.201 with HTTP; Tue, 19 Nov 2013 03:06:13 -0800 (PST)
In-Reply-To: <CALJZF3jSjqbfpZkfPhq=4E7iDFGCpBS=mJjaZmgNhJOY5BQqDQ@mail.gmail.com>
References: <CALJZF3hPY01c9EoVg3HYZec8TzuKwNkxZQvE58mtwh-WouUJfQ@mail.gmail.com>
	<528B3C03.5090804@gmail.com>
	<CALJZF3jSjqbfpZkfPhq=4E7iDFGCpBS=mJjaZmgNhJOY5BQqDQ@mail.gmail.com>
Date: Tue, 19 Nov 2013 12:06:13 +0100
Message-ID: <CAH-PCH5Nu+hFfJPEuvT8d=Frm6rAxSJxK8hiXv1wThtyezcfrg@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: Alexey Zakhlestin <indeyets@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b6dc1521615bb04eb85a729
Subject: Re: [PHP-DEV] [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA)
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b6dc1521615bb04eb85a729
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 19, 2013 at 11:48 AM, Michael Wallner <mike@php.net> wrote:

> On 19 November 2013 11:22, Alexey Zakhlestin <indeyets@gmail.com> wrote:
>
> > We can't break BC in 5.x, so the way to go is:
> >
> > 1. implement underlying changes
>
> It already is in master since a few weeks.
>
> > 2. restore backwards compatibility (HTTP_RAW_POST_DATA should be
> > auto-populated in all cases when it is populated now)
>
> That defeats the entire change.
>
> > 3. always_populate_raw_post_data should be introduced for BC purposes
> >
> > 4. Is it possible to detect usage of HTTP_RAW_POST_DATA and give
> > E_DEPRECATED while doing so?
>
> AFAICS no, it is a standard global variable.
>
> > 5. remove HTTP_RAW_POST_DATA support in master (thinking about 6.x)
>
> It already is in master.
>
>
I guess Alexey is trying to say that we could deprecate the usage of
$HTTP_RAW_POST_DATA in 5.6, but this feature should go(stay) to master(and
target the next major) as it breaks BC, which we can't do in a minor
version.
And while I agree with it, let's see what others think.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7b6dc1521615bb04eb85a729--