Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78018
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender)
MIME-Version: 1.0
Sender: are.you.winning@gmail.com
In-Reply-To: <etPan.543d323e.515f007c.12d@Mikes-iMac.local>
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>
	<CAGAGxbYBO_E-tf7SipgRDgy-kQZiwF96QGSAwGcJpc2zZ=GGNw@mail.gmail.com>
	<4240E494-94E6-4FC9-BB84-C30FFA69129C@benramsey.com>
	<CAGAGxbaZjq-f=i3CvcNOa--goiL9kxfp+LJRooA7mgo4wEd_RA@mail.gmail.com>
	<69EB8F97-7CFC-44E0-8B2D-C2230ADAC87F@ajf.me>
	<etPan.543d2e49.3d1b58ba.12d@Mikes-iMac.local>
	<F4F3722F-4335-42C9-AEFC-5D17407E3A34@benramsey.com>
	<etPan.543d323e.515f007c.12d@Mikes-iMac.local>
Date: Tue, 14 Oct 2014 15:53:52 +0100
Message-ID: <CAGAGxbbWLTW9MBkyYmy1kTgWw_RTfcDE_pAv6uCe4udKSC7gdA@mail.gmail.com>
To: Mike Dugan <mike@mjdugan.com>
Cc: Ben Ramsey <ben@benramsey.com>, Andrea Faulds <ajf@ajf.me>, Kris Craig <kris.craig@gmail.com>, 
	Andrey Andreev <narf@devilix.net>, Chris Wright <cw@daverandom.com>, 
	PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: cw@daverandom.com (Chris Wright)

On 14 October 2014 15:25, Mike Dugan <mike@mjdugan.com> wrote:
> On October 14, 2014 at 10:21:34 AM, Ben Ramsey (ben@benramsey.com) wrote:
>
>
> On Oct 14, 2014, at 9:08 AM, Mike Dugan <mike@mjdugan.com> wrote:
>
>> On October 14, 2014 at 10:04:00 AM, Andrea Faulds (ajf@ajf.me) wrote:
>>>
>>>
>>> So $_QUERY and $_FORM, then. That sounds about right.
>>>
>>
>> Did I just name a global variable? W00t!
>>
>> Anyhow, yeah neither one is technically 100% correct, but like Andrea
>> said, the majority of usage will be from forms and query strings with
>> parameters. At any rate, it=E2=80=99s makes more sense semantically in t=
he context
>> of what the var actually contains than $_GET and $_POST ever will.
>>
>
> +1
>
> I=E2=80=99m cool with $_QUERY and $_FORM. They make much more sense and d=
on=E2=80=99t try to
> use HTTP verbs, which can confuse the content and semantics of the data t=
hey
> contain. Plus, they would just alias $_GET and $_POST, respectively, righ=
t?
>
> -Ben
>
>
>
>
>
> That=E2=80=99s my understanding. There=E2=80=99s also some discussion abo=
ut deriving data
> from $_POST/$_FORM that is intended for use with other HTTP verbs, I=E2=
=80=99m still
> trying to ascertain exactly what was in mind there (Andrea I think you
> suggested that?)

Well the top of the discussion was suggesting $_PUT and $_DELETE,
which would imply that entity bodies are processed for all HTTP verbs,
the more semantic names for the existing variables came out of this
suggestion (as putting data from other request methods into $_POST
isn't very intuitive).

I'm about +0.5 on both. The name aliases are more semantically
correct, and that's a good thing, but also not entirely necessary.
Processing entity bodies regardless of request method (baring in mind
that this is still content type dependent) is certainly harmless and
may be useful to someone somewhere.

I still think this deflects focus from what would be more useful here:
a native request abstraction *object*, which provides access to all
elements of the *request* without a) splitting them up into distinct
global data stores as the current $_GET, $_POST, $_COOKIE does and b)
mixing request data in with server environment data, as $_SERVER
currently does.