Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69507
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.169 as permitted sender)
Message-ID: <5252D84B.5080802@gmail.com>
Date: Mon, 07 Oct 2013 16:50:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAH8MpnkB42pmuZLOAbETj=v2kGXODkwfPewW57XehAB77wUY7g@mail.gmail.com>
In-Reply-To: <CAH8MpnkB42pmuZLOAbETj=v2kGXODkwfPewW57XehAB77wUY7g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: HTTP supergloblas and request body/query (was:
 Parsing PUT data)
From: rowan.collins@gmail.com (Rowan Collins)

Daniel Lowrey wrote (on 02/10/2013):
> Something like the following would be an infinitely superior solution:
>
> interface HttpRequest {

While having a quick look for userland parsing functions earlier, I came 
upon the PECL http extension, which includes this all-singing object:

http://www.php.net/manual/en/class.httprequest.php

As for this:

> 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. PHP even allows the convenient field_name[]= and 
field_name[key]= notations for building multi-dimensional arrays.

This is all a convenience wrapper, and a consistent low-level API would 
be good, but alternative high-level APIs can be built from a few 
fundamental building blocks (e.g. getting the basic raw request parts as 
strings, parsing strings in various form encodings) without building a 
whole HTTP framework into the core.

Regards,
-- 
Rowan Collins
[IMSoP]