Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78070
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <543D85E6.2020507@lerdorf.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>
	<543D47C1.9050009@lerdorf.com>
	<etPan.543d4c0e.216231b.12d@Mikes-iMac.local>
	<543D4CE1.5000109@lerdorf.com>
	<543D6864.10508@gmail.com>
	<543D85E6.2020507@lerdorf.com>
Date: Tue, 14 Oct 2014 14:38:43 -0700
Message-ID: <CAKOpQSyTSZeXppZ-f9OeNfA9=Q58jte1fH6zcuzxYZ+qK7-6JA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c32246dfdd4c050568d6dd
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: kris.craig@gmail.com (Kris Craig)

--001a11c32246dfdd4c050568d6dd
Content-Type: text/plain; charset=UTF-8

On Tue, Oct 14, 2014 at 1:21 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 10/14/2014 11:16 AM, Rowan Collins wrote:
> > On 14/10/2014 17:18, Rasmus Lerdorf wrote:
> >> I think 20+ years of history has proven this to be a non-issue. Of all
> >> the things that people get confused by in PHP, $_GET/$_POST are right
> >> near the bottom of the list.
> >
> > The popularity of REST is what has changed this. Until people started
> > writing RESTful APIs, only two HTTP request types were in common use.
> > Nobody was confused about where PUT method data would end up, because
> > nobody processed any PUT methods.
> >
> >> It makes no sense to me to make $_BODY an alias for $_POST. $_POST
> >> implies the default body encoding that a broswer performs on a POST
> >> request. Making an alias called $_BODY that doesn't contain the body of
> >> a request unless it is "POST"-encoded would be super confusing.
> >
> > The encoding has no relationship with the request type, even in browsers
> > - the default encoding of a POST form is actually the same encoding used
> > to produce a URL form a GET form.
>
> Sure, but $_GET/$_POST do. They were not named to match HTTP primitives.
> They were named to match form methods. As in form method="get" and
> method="post". And here the default encoding the browsers use for these
> two methods definitely matter.
>
> -Rasmus
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
I understand that that was the original intent. However, the use cases have
expanded beyond simply handling HTML form submissions.  People are writing
REST APIs using PHP now, and having GET/POST but not PUT/DELETE has indeed
led to confusion.  I only posted this after doing a Google search and
finding tons of results from people mistakenly asking why PHP doesn't
handle PUT/DELETE requests or complaining how the lack of aliases for
PUT/DELETE leads to inconsistency in the code.

Personally, I like the idea of using more appropriately named aliases,
particularly if they're roughly the same number of characters.  However, we
would need to allow at least several years for people to adopt the new
globals before deprecating $_GET and $_POST.  Ultimately, they will either
need to be deprecated or the $_PUT and $_DELETE aliases will need to be
added, otherwise the issue I raised would remain unresolved.

--Kris

--001a11c32246dfdd4c050568d6dd--