Re: New globals for PUT and DELETE
| From: | Rasmus Lerdorf | Date: | Tue, 14 Oct 2014 15:56:49 +0000 |
| Subject: | Re: New globals for PUT and DELETE | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78028@lists.php.net to get a copy of this message | ||
On 10/14/2014 06:29 AM, Andrea Faulds 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 $_QUERY (for $_GET) and $_BODY
> (for $_POST)? Then the variable set finally makes sense, but isn’t 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?
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.
I think the pedantry level around this is rather high. Nobody is
actually confused about $_GET and $_POST and how and when to use them.
Adding vague aliases adds confusion to something that had no confusion
before.
-Rasmus