Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78486
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
In-Reply-To: <CAL+t6cFh77D0FufKGy_OeLO7O0=ky46Zv8S=oTLFP8VnZRtCvw@mail.gmail.com>
Date: Thu, 30 Oct 2014 20:24:23 +0000
Cc: Florian Margaine <florian@margaine.com>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <36B5E957-01C0-40F2-B4CE-5B02D11ACA14@ajf.me>
References: <CAL+t6cGt8B+X4ptWbyo6zm_xoyBOJC4QeiH6DjCxHX11CPWm_g@mail.gmail.com> <CABRjmp9p=+zGiqn_nuVJcDAK0po98FnDhb7wTmG66tob4u0GOw@mail.gmail.com> <CAL+t6cFh77D0FufKGy_OeLO7O0=ky46Zv8S=oTLFP8VnZRtCvw@mail.gmail.com>
To: Sherif Ramadan <theanomaly.is@gmail.com>
Subject: Re: [PHP-DEV] New Standardized HTTP Interface
From: ajf@ajf.me (Andrea Faulds)


> On 30 Oct 2014, at 19:49, Sherif Ramadan <theanomaly.is@gmail.com> =
wrote:
>=20
> Well, let's look at how well providing implementation has worked out =
for
> PHP so far.
>=20
> GPC variables are implementation. They pose rigidity to userland code =
for a
> number of reasons. For example, if you do send a PUT request to PHP, =
PHP
> will not bother populating GPC at all. Instead it leaves the user to =
define
> their own handling from the input stream directly. If you do send =
GET/POST
> requests to PHP, the variable names can be mangled and $_GET/$_POST =
are
> treated differently for encoding as one is run through url_decode and =
the
> other is not.

We could just fix these problems rather than adding an entirely new =
implementation.
--
Andrea Faulds
http://ajf.me/