Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78523
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5453C250.8090803@gmail.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>
Date: Fri, 31 Oct 2014 13:27:40 -0400
Message-ID: <CAL+t6cEH7PPMu2G=e4NQau-iOznkG31-d187EMCDY0LFeew68g@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2400c5ef06f0506bb5023
Subject: Re: [PHP-DEV] New Standardized HTTP Interface
From: theanomaly.is@gmail.com (Sherif Ramadan)

--001a11c2400c5ef06f0506bb5023
Content-Type: text/plain; charset=UTF-8

On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

>
> Let me repeat my question:
>
> Say I write a class "AwesomeHTTPReceive implements HttpMessageReceive",
> what do I then do with this class in order for it to perform any actions?
>
> How does PHP know that my class is the one it should populate, or when
> that population should happen?
>


It wouldn't. You would need to extend the base class, since it already
implements the necessary interface. PHP would simply call on the last
subtype of HttpRequest during the request init phase. Of course, this is an
implementation detail as of now. There could certainly be other/better ways
to accomplish this. I just want to keep it as simple as possible for now
without introducing more configuration nightmares that people often
complain about. I really don't like the idea of adding yet another INI
directive to control this behavior (making it harder to port).

What do you propose?

--001a11c2400c5ef06f0506bb5023--