Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96159
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.180 as permitted sender)
To: internals@lists.php.net
References: <DE0439B3-29F4-4BC6-B92A-A7630BE17196@gmail.com>
Message-ID: <1e5a2abd-0044-5d57-d4b2-ddbbd3577639@gmail.com>
Date: Mon, 26 Sep 2016 22:32:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <DE0439B3-29F4-4BC6-B92A-A7630BE17196@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Server-Side Request/Response Objects
From: rowan.collins@gmail.com (Rowan Collins)

On 26/09/2016 20:37, Paul Jones wrote:
> tl;dr: Gauging interest in an extension for server-side PHP request and response objects (*not*  HTTP messages per se; see below) prior to writing an RFC for them on the wiki.

This sounds like an interesting project, but I have a few questions.

First, the obvious one: why does this need to be an extension and/or 
built into core? Are there reasons such as performance for implementing 
this in C rather than PHP? Does it provide functionality that is hard to 
implement in a userland library?

You mention that it is not just an HTTP wrapper, but although you 
mention researching other frameworks, I can't see any reference to PSR-7 
[http://www.php-fig.org/psr/psr-7/]. What do you see as the relationship 
between your proposal and that standardisation effort?

Regarding the design of the objects themselves, why is stdRequest 
property-only, but stdResponse method-only? The asymmetry feels awkward 
to me.

I think the most interesting parts are those that attempt to rationalise 
$_SERVER, and I think a library (or built-in functionality) devoted to 
those could be very useful. Some of that overlaps with PSR-7, but that 
standard doesn't go into depth on things like Accept headers, 
Authentication, etc.

Like I say, it's an interesting idea, but I'm not sure how it fits in 
with the wider ecosystem.

Regards,

-- 
Rowan Collins
[IMSoP]