Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76607
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH4MEg31v624jNV8rG73j4OWOakBApVx3QMUdCqP8ui5ZA@mail.gmail.com>
References: <CAPRqa+G7_quRQ-NR04DChPEZeevuRBHX_1GbOCO+N4VXnzrCTw@mail.gmail.com>
	<CAH-PCH4MEg31v624jNV8rG73j4OWOakBApVx3QMUdCqP8ui5ZA@mail.gmail.com>
Date: Sun, 17 Aug 2014 16:10:01 +0300
Message-ID: <CAPRqa+Ea2uTLK6W+HuvPaHtLpYRGZv+BFmQQ5L5m3giOjK3cOQ@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b2e4eded710f20500d2f8f3
Subject: Re: [PHP-DEV] Native support - PUT request, multipart form data
From: park.framework@gmail.com (Park Framework)

--047d7b2e4eded710f20500d2f8f3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2014-08-17 12:22 GMT+03:00 Ferenc Kovacs <tyra3l@gmail.com>:

>
>
>
> On Sun, Aug 17, 2014 at 12:41 AM, Park Framework <park.framework@gmail.co=
m
> > 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 versio=
n,
> so you can try targetting 5.6.next with the rfc but there is a chance tha=
t
> 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 name=
d
> superglobals, but ofc. killing off $_GET/$_POST could only happen in a
> major version.
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>

I have never written RFC, and I'm not a developer in C/C++.
Will correct if the RFC write the author of the patch.
Thank you.

--047d7b2e4eded710f20500d2f8f3--