Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78003
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGAGxbYkj2ZMo8Zx1w-NdE2dZfZPkenWrCOaZAfi0nMVT56jxg@mail.gmail.com>
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>
	<776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me>
	<CAKOpQSwRtSU1LNmftyY1b09SONBCfwS-qiMK4gct6uFiW3CSjw@mail.gmail.com>
	<CAPhkiZwb13FmX+sQLx0Ki52KuwJ4HWTj-84UqcZq3GYPFL8Tnw@mail.gmail.com>
	<E8F7D721-767C-4E6E-B0BB-F0DEFEB308B2@ajf.me>
	<CAF9U7z_0cgwWFEoShU9rJhoOZttztcZk_NAqoXnSuAro-w3kew@mail.gmail.com>
	<8CB055D4-F164-4DF3-B019-684BAE7E016E@ajf.me>
	<etPan.543d27fe.2ae8944a.12d@Mikes-iMac.local>
	<CAKOpQSzU4mUEDRX25z8TCbtDD04rDBBmF439p_Q65g2jjDMcpw@mail.gmail.com>
	<CAGAGxbYkj2ZMo8Zx1w-NdE2dZfZPkenWrCOaZAfi0nMVT56jxg@mail.gmail.com>
Date: Tue, 14 Oct 2014 06:57:44 -0700
Message-ID: <CAKOpQSzykDwF1pngGA=pcew2TT4GiaC3cR6v1cza0kUqAzkj7Q@mail.gmail.com>
To: Chris Wright <cw@daverandom.com>
Cc: Mike Dugan <mike@mjdugan.com>, Andrea Faulds <ajf@ajf.me>, 
	Kristopher <kristopherwilson@gmail.com>, PHP internals list <internals@lists.php.net>, 
	Andrey Andreev <narf@devilix.net>
Content-Type: multipart/alternative; boundary=047d7b67682c4b8fb90505626652
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: kris.craig@gmail.com (Kris Craig)

--047d7b67682c4b8fb90505626652
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 14, 2014 at 6:50 AM, Chris Wright <cw@daverandom.com> wrote:

> On 14 October 2014 14:46, Kris Craig <kris.craig@gmail.com> wrote:
> > On Tue, Oct 14, 2014 at 6:41 AM, Mike Dugan <mike@mjdugan.com> wrote:
> >
> >>
> >> On October 14, 2014 at 9:31:15 AM, Andrea Faulds (ajf@ajf.me) wrote:
> >>
> >>
> >> On 14 Oct 2014, at 14:27, Kristopher <kristopherwilson@gmail.com>
> wrote:
> >>
> >> > $_HTTP_REQUEST_BODY and $_HTTP_QUERY_STRING for nostalgia's sake.
> >>
> >> Ew, non-superglobals.
> >>
> >> But $_REQUEST_BODY and $_QUERY_STRING are a bit lengthy. Perhaps $_QUE=
RY
> >> (for $_GET) and $_BODY (for $_POST)? Then the variable set finally mak=
es
> >> sense, but isn=E2=80=99t too long:
> >>
> >> * $_QUERY - query string parameters
> >> * $_BODY - request body parameters
> >> * $_REQUEST - query string and request body parameters
> >>
> >> Makes more sense than $_GET and $_POST.
> >>
> >> Any objections?
> >>
> >> --
> >> Andrea Faulds
> >> http://ajf.me/
> >>
> >>
> >> +1 for this. This would hopefully also eliminate the confusion for new
> >> developers (or not-so-new developers) who don=E2=80=99t quite understa=
nd that
> $_GET
> >> and $_POST don=E2=80=99t strictly relate to their HTTP verbs of the sa=
me name.
> >>
> >> --
> >>
> >> Mike Dugan
> >>
> >> mike@mjdugan.com
> >>
> >
> > That could work, though the BC breakage will be extreme.  I'm not sure =
if
> > that's worth it even in a major version increment.  On the other hand,
> > making $_PUT and $_DELETE available wouldn't break anything and wouldn'=
t
> > require re-training for devs.
>
> ...but is also the wrong solution. It's not scalable,


How is it not scalable, exactly?  It's just a couple aliases.


> and the only
> sensible way to implement them would be as aliases of $_POST, because
> they would contain the same data. How does this fundamentally differ
> from $_BODY (or whatever)?
>

It's not supposed to functionally differ.  It's supposed to create some
better consistency and make it easier for devs to differentiate between
different REST methods when retrieving data.  If REQUEST_METHOD is PUT,
then I can set the parsed params to the value of $_PUT.  The aliases match
the methods used, making the code that much more readable and scalable.

--Kris

--047d7b67682c4b8fb90505626652--