Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78527
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5453D6D5.2070705@garfieldtech.com>
References: <CAL+t6cGt8B+X4ptWbyo6zm_xoyBOJC4QeiH6DjCxHX11CPWm_g@mail.gmail.com>
	<5452B87B.5040009@garfieldtech.com>
	<CAL+t6cHqQL-TaurfG887qxeyeVZPCxQcnY_BrtD-oHCS196HQw@mail.gmail.com>
	<0B797CE3-7AFA-4330-9A98-D3CAFC6D6072@ajf.me>
	<CAL+t6cGanxv3dJONcECupw6Cfzup4s6At6tEcK_=Qagn67RNjw@mail.gmail.com>
	<5453B114.6050400@gmail.com>
	<CAL+t6cFCToJJGiCb8JhNe9oQws5UuBdKw+ot3rjUBQQr=7=Bxw@mail.gmail.com>
	<5453C250.8090803@gmail.com>
	<CAL+t6cEH7PPMu2G=e4NQau-iOznkG31-d187EMCDY0LFeew68g@mail.gmail.com>
	<CABRjmp-b1jGD1SBTxmnJFLKi++WbL4TBggijN+VfSjRjPMJYPQ@mail.gmail.com>
	<CAL+t6cF7t7shs78xSiBfGxZSCqh5zcU-B_WWjK5J9ebiB=PTQA@mail.gmail.com>
	<5453D6D5.2070705@garfieldtech.com>
Date: Fri, 31 Oct 2014 14:52:33 -0400
Message-ID: <CAL+t6cEyLFqQ9cRW3uiE-pRMsMEyOywAhWWDtg5zFFL-U2mogg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d040fa004eec7390506bc7f4a
Subject: Re: [PHP-DEV] New Standardized HTTP Interface
From: theanomaly.is@gmail.com (Sherif Ramadan)

--f46d040fa004eec7390506bc7f4a
Content-Type: text/plain; charset=UTF-8

So for the purposes of this discussion and in an effort to remain on-topic
and productive, let's keep all of the FIG/PSR and other third party efforts
out of the discussion unless it is intended to improve/help this particular
RFC. Please keep in mind that this is a PHP internals discussion and not a
FIG/PSR discussion. This RFC is about core PHP and I really don't care how
many competing ideas exist out there that are closely or mildly related to
this RFC.

This RFC has two primary goals in mind:

1) Expose the parsing/handling of the HTTP request to userland in a
consistent way
2) Avoid having the request parsed/mangled at multiple levels during the
request by presenting one central place to handle the parsing

These goals can not be achieved purely in userland, because you would
potentially have to do the parsing step twice. I wish to make it possible
for the user to override that with their own implementation just like they
can override the Session handler with the Session interface.

How we end up deciding to do that may change from my initial proposal, and
that's fine, but let's focus on that rather than getting off topic about
other third party efforts.

Thanks!

--f46d040fa004eec7390506bc7f4a--