Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69436
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
Sender: mike.php.net@gmail.com
Date: Wed, 2 Oct 2013 08:59:15 +0200
Message-ID: <CALJZF3hq1FVTJUGwq9PAt+6joDhmuoXPR9Z8cxTPvafUmek9wg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: HTTP supergloblas and request body/query (was: Parsing PUT data)
From: mike@php.net (Michael Wallner)

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).

Further, I propose to remove the POST method restriction for handling
request bodies and solely rely on the content type to trigger the
parser(s). (*)

There are already parsers for application/x-www-form-urlencoded and
multipart/form-data in the core.  One could think of providing an API
to add content type handlers from extensions, ext/json may be an
example, like it is hacked into pecl_http-v2.

Thoughts, objections, insults?

(*) We'd probably have to revisit all *post* INI variables, though.

-- 
Regards,
Mike