Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77980
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender)
Message-ID: <543D2308.4050403@gmail.com>
Date: Tue, 14 Oct 2014 14:20:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>	<776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> <CAKOpQSwRtSU1LNmftyY1b09SONBCfwS-qiMK4gct6uFiW3CSjw@mail.gmail.com>
In-Reply-To: <CAKOpQSwRtSU1LNmftyY1b09SONBCfwS-qiMK4gct6uFiW3CSjw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: rowan.collins@gmail.com (Rowan Collins)

Kris Craig wrote (on 14/10/2014):
> The problem with that approach though is that it would not be RESTful.  I'm
> developing a REST API (with the goal of 100% REST compliance) and having
> PUT/DELETE variables mixed in with $_POST would not only be
> counter-intuitive, but it would just present a new roadblock.

This makes no sense; there is no such thing as "PUT/DELETE variables" in 
HTTP, any more than there is such things as "POST variables".

Just imagine that the variables are called $_QUERY_STRING and 
$_REQUEST_BODY. They should be completely orthogonal to the request method.

Note that this is already true to an extent - you can access the query 
string through $_GET on a POST request, and $_POST will exist as an 
empty array.