Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76600
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPRqa+G7_quRQ-NR04DChPEZeevuRBHX_1GbOCO+N4VXnzrCTw@mail.gmail.com>
References: <CAPRqa+G7_quRQ-NR04DChPEZeevuRBHX_1GbOCO+N4VXnzrCTw@mail.gmail.com>
Date: Sun, 17 Aug 2014 11:22:15 +0200
Message-ID: <CAH-PCH4MEg31v624jNV8rG73j4OWOakBApVx3QMUdCqP8ui5ZA@mail.gmail.com>
To: Park Framework <park.framework@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c11fd8478e490500cfcac7
Subject: Re: [PHP-DEV] Native support - PUT request, multipart form data
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c11fd8478e490500cfcac7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 17, 2014 at 12:41 AM, Park Framework <park.framework@gmail.com>
wrote:

> This is necessary for convenient use RESTful API.
>
> file_get_contents('php://input')  - Very inconvenient
>
> I would like to finally get native support for PHP, preferably version 5.=
6
>

feel free to create an rfc/implementation, I don't think it would be wise
to introduce it in 5.6.x(there is zero chance to have this in 5.6.0), but
our releaseprocess allows small self-contained features in a micro version,
so you can try targetting 5.6.next with the rfc but there is a chance that
some people will vote no who otherwise would support this in 5.next or 7.0.
I tend to agree that it would be better to move away from the method named
superglobals, but ofc. killing off $_GET/$_POST could only happen in a
major version.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c11fd8478e490500cfcac7--