Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69509
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Date: Mon, 7 Oct 2013 13:19:03 -0400
Message-ID: <CAH8MpnkgubiJ3VUkRN9r1tUzzQ2m-Cr13-TViu2Z5atMy49NiA@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Cc: rowan.collins@gmail.com
Content-Type: multipart/alternative; boundary=001a11c2ef0245bfbc04e829d95d
Subject: Re: Re: HTTP supergloblas and request body/query (was: Parsing PUT data)
From: rdlowrey@gmail.com (Daniel Lowrey)

--001a11c2ef0245bfbc04e829d95d
Content-Type: text/plain; charset=ISO-8859-1

>> You can't efficiently model an HTTP request with associative arrays.
Period.

> The fact is that for 99% of use cases, yes you can, and developers
> happily do so.

Leaky abstraction is leaky. If this is truly an efficient model of the HTTP
request then why do we fragment it out into $_SERVER and $_COOKIES and
$_FILES and $_POST and $_GET and php://input? I don't know what your
definition of "efficiently model" is, but it must be different from mine.
Array Oriented Programming !== design.

> without building a  whole HTTP framework into the core.

I'm devoutly anti-framework and I don't think anyone is actually advocating
this. If you read closely I'm arguing *against* adding more superglobals.
I'm also against changing the names of the existing arrays as any
improvement is far outweighed by the massive BC implications of such a
change. I personally don't care whether or not a better request model is
implemented in core -- I've already unlearned the bad-habits ingrained at
the language-level.

--001a11c2ef0245bfbc04e829d95d--