Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70203
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
Message-ID: <528B5221.5050502@gmail.com>
Date: Tue, 19 Nov 2013 15:57:21 +0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Michael Wallner <mike@php.net>
CC: PHP internals <internals@lists.php.net>
References: <CALJZF3hPY01c9EoVg3HYZec8TzuKwNkxZQvE58mtwh-WouUJfQ@mail.gmail.com>	<528B3C03.5090804@gmail.com> <CALJZF3jSjqbfpZkfPhq=4E7iDFGCpBS=mJjaZmgNhJOY5BQqDQ@mail.gmail.com>
In-Reply-To: <CALJZF3jSjqbfpZkfPhq=4E7iDFGCpBS=mJjaZmgNhJOY5BQqDQ@mail.gmail.com>
OpenPGP: id=1D219F11
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="A4icPPTEB7g5scnedhc9lkL0cCc6xQPXx"
Subject: Re: [PHP-DEV] [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA)
From: indeyets@gmail.com (Alexey Zakhlestin)

--A4icPPTEB7g5scnedhc9lkL0cCc6xQPXx
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 19.11.13, 14:48, Michael Wallner wrote:
> On 19 November 2013 11:22, Alexey Zakhlestin <indeyets@gmail.com> wrote=
:
>=20
>> 2. restore backwards compatibility (HTTP_RAW_POST_DATA should be
>> auto-populated in all cases when it is populated now)
>=20
> That defeats the entire change.

Not really.
We would still have a new implementation, which has a smaller diff to
master, so can be kept in sync.

I know the stance against new ini-settings, but I wonder if we could
introduce an ini-setting which would be equivalent to python's
"from future import =E2=80=A6"

If this is an option, then HTTP_RAW_POST_DATA could be optimized away
when this option is turned on (default is obviously "Off").


>> 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?
>=20
> AFAICS no, it is a standard global variable.

that leaves us with deprecation via documentation, then


--=20
Alexey Zakhlestin
CTO at Grids.by/you
https://github.com/indeyets
PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc


--A4icPPTEB7g5scnedhc9lkL0cCc6xQPXx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJSi1IqAAoJEMkJcRxZdR27pQYIAIdLPrZC8IORI5tBxx4m0LIM
A9UqohnXIlZNavN8WhhrM5pciCFztYLm4/YXC2NVU4jp5axsMvxyPw3pC4ne7mHY
M5fg+UrnHHwScitIDgWMDi4+0ihbRYdd3EMh0wUXKMekVgxDwZH3elE7RbCtFAWf
pc6NQmlDunTD2dE0NK4yAe6ZuXyV14p86v1ClS+sy70c3T7dbo21QnyrHzXjmAy1
gZSVYJSeZlrnkCzVDRIoHnx+X97W5PR1PByeIrEUTxG5A8n2OWYffEgE5LMwv5wH
cgNoyhWqFGsz7ONmvm+QJIXRTBflB39G4iS+n64ZPfldSufIRZJJ5brNNfqWt6w=
=IGmx
-----END PGP SIGNATURE-----

--A4icPPTEB7g5scnedhc9lkL0cCc6xQPXx--