Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77979
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9CAD580B-48C1-4D91-B761-20F8A9804A66@benramsey.com>
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>
	<9CAD580B-48C1-4D91-B761-20F8A9804A66@benramsey.com>
Date: Tue, 14 Oct 2014 06:17:16 -0700
Message-ID: <CAKOpQSynzFJQc7uOwuV6-cSNtvW_78pVSxcNvpFqkauFBC0ZHA@mail.gmail.com>
To: Ben Ramsey <ben@benramsey.com>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0139fc288e616e050561d533
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: kris.craig@gmail.com (Kris Craig)

--089e0139fc288e616e050561d533
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 14, 2014 at 6:09 AM, Ben Ramsey <ben@benramsey.com> wrote:

> On Oct 14, 2014, at 7:47 AM, Kris Craig <kris.craig@gmail.com> wrote:
>
> > Hey guys,
> >
> > Does anybody know why we have $_GET and $_POST, but not $_PUT and
> > $_DELETE?  As far as I can tell, the only way to get these out currentl=
y
> is
> > to parse their values by reading the incoming stream directly.
> >
> > Is there a reason why we don't want this or is it just that nobody has
> > actually written it yet?
> >
> > =E2=80=94Kris
>
> This is due to the history of HTML forms sending POST requests with the
> Content-Type application/x-www-form-urlencoded. That is, all the fields a=
re
> key/value pairs and may be easily converted into a PHP array. If you use
> POST with application/json, nothing appears in $_POST, for example.
>
> In practice, we could support $_PUT and $_DELETE for requests that use
> application/x-www-form-urlencoded, but most folks implementing PUT and
> DELETE do not use application/x-www-form-urlencoded for these requests.
>
> I would venture to say that most people implementing PUT requests accept
> application/json and most DELETE requests have no body at all. So, $_PUT
> and $_DELETE superglobals wouldn=E2=80=99t make sense.
>
> -Ben
>
>
I'm not following your logic, Ben.  Just because there are a lot of people
out there who don't understand REST, doesn't mean we shouldn't add support
for the other methods.  Besides, if anyone wants to develop a truly RESTful
API in PHP-- which a lot of devs are doing every day-- not giving them
$_PUT and $_DELETE is what wouldn't make any sense.  I'm writing an API now
and the lack of those two globals has proven to be a real pain in the ass.
The Content-Type argument really isn't an issue since the API developer
should be setting the right headers for the request method, anyway.

I don't see any gain in not making those globals available.  All it does is
present both inconvenience and inconsistency for any REST-based project.

--Kris

--089e0139fc288e616e050561d533--