Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69461
Return-Path: <mike.php.net@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 53384 invoked from network); 2 Oct 2013 17:59:21 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 2 Oct 2013 17:59:21 -0000
Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
X-PHP-List-Original-Sender: mike.php.net@gmail.com
X-Host-Fingerprint: 209.85.215.49 mail-la0-f49.google.com  
Received: from [209.85.215.49] ([209.85.215.49:46109] helo=mail-la0-f49.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id C5/EC-23255-8FE5C425 for <internals@lists.php.net>; Wed, 02 Oct 2013 13:59:21 -0400
Received: by mail-la0-f49.google.com with SMTP id ev20so958187lab.8
        for <internals@lists.php.net>; Wed, 02 Oct 2013 10:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type:content-transfer-encoding;
        bh=6T6Samkr2rhExKmMY1scldoWgKJ/aEtj6Q8GYns9wJc=;
        b=oQl5tgfDc7zFb6kRU6TGe45wXjxiJMYqafUdnF4AsH273oU8uBxeNB2NwRLm2pMbeH
         UwnxMukEUwV3CVrxKhblrcHMaHCTVtvVL9fOjlFLw74CcIr93FSfLk1bQZh8jT58zNZq
         JFOGqWG9TggCtJR6zbmtS45RGsWO9Nx4l1Cke6tG/JelGxTD0SCcAACk6LfYZXzugB+u
         Dgvmr28WedzhW2hp6bcx5CNVTuXLKgbqxE4fe2QvulVAMjmGIZ28la5iMOjPXEyhS9X/
         KUrt3D3hDoR++wwnRcNSM0JA1FVhO1Je1cfkbxqgvei2Z/iXV2IizEfRAGurXItC0ZfP
         Rtxg==
MIME-Version: 1.0
X-Received: by 10.112.29.17 with SMTP id f17mr2172621lbh.45.1380736758079;
 Wed, 02 Oct 2013 10:59:18 -0700 (PDT)
Sender: mike.php.net@gmail.com
Received: by 10.114.184.19 with HTTP; Wed, 2 Oct 2013 10:59:17 -0700 (PDT)
In-Reply-To: <1380723023.19591.24.camel@guybrush>
References: <CALJZF3hq1FVTJUGwq9PAt+6joDhmuoXPR9Z8cxTPvafUmek9wg@mail.gmail.com>
	<1380723023.19591.24.camel@guybrush>
Date: Wed, 2 Oct 2013 19:59:17 +0200
X-Google-Sender-Auth: oj2-H8qwaIPmD6JbvNEWkZZGI_c
Message-ID: <CALJZF3g9WaXADPfBYgn5FQCv7njcpSRgo0gERbjYCirvbx0maQ@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] HTTP supergloblas and request body/query (was: Parsing
 PUT data)
From: mike@php.net (Michael Wallner)

On 2 October 2013 16:10, Johannes Schl=C3=BCter <johannes@schlueters.de> wr=
ote:
> On Wed, 2013-10-02 at 08:59 +0200, Michael Wallner wrote:
>> Since ever people are confused by _GET and _POST superglobals,
>> because, despite their name, they do not (really) depend on the
>> request method.  Therefor I propose to phase out $_GET and name it
>> $_QUERY and I propose to phase out $_POST and name it $_FORM (I'm not
>> 100% confident with the latter yet, though).
>
> The later is certainly misleading. The current naming corresponds to
> HTML forms.
>
>    <form method=3D"GET">   -> $_GET
>    <form method=3D"POST">  -> $_POST

Heh, pretty good observation! Didn't think about that. Still not
buying. $_FORM is derived from "application/x-www-form-urlencoded"
resp. "multipart/form-data" and $_QUERY is obvious.


> I agree that the naming from a HTTP/REST etc. perspective is misleading,
> but unless we have a clearly better naming I would resist from changing
> these.

Not only for REST, but in general IMHO, e.g: <form method=3D"POST"
action=3D"?see=3Dgotcha">


>
> Changing these leads to an incompatibility which can not be emulated
> (ignoring runkit there is no way for a user to create a custom super
> global)

Valid point. Though, with a long enough time frame it could be done.


> In case that is ignored please mind other related areas, i.e.
> filter_input() to make sure the resulting new language is consistent.

Yeah, well, there's a lot attached to that cumbersome naming, e.g. all
*_post_* INI settings etc.
I should have just resisted proposing that change, but I figured
testing for backing was cheap.

--=20
Regards,
Mike