Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78525
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABRjmp-b1jGD1SBTxmnJFLKi++WbL4TBggijN+VfSjRjPMJYPQ@mail.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>
	<CAL+t6cEH7PPMu2G=e4NQau-iOznkG31-d187EMCDY0LFeew68g@mail.gmail.com>
	<CABRjmp-b1jGD1SBTxmnJFLKi++WbL4TBggijN+VfSjRjPMJYPQ@mail.gmail.com>
Date: Fri, 31 Oct 2014 13:38:15 -0400
Message-ID: <CAL+t6cF7t7shs78xSiBfGxZSCqh5zcU-B_WWjK5J9ebiB=PTQA@mail.gmail.com>
To: Florian Margaine <florian@margaine.com>
Cc: PHP Internals <internals@lists.php.net>, Rowan Collins <rowan.collins@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bb047dc3bf9330506bb766f
Subject: Re: [PHP-DEV] New Standardized HTTP Interface
From: theanomaly.is@gmail.com (Sherif Ramadan)

--047d7bb047dc3bf9330506bb766f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 31, 2014 at 1:32 PM, Florian Margaine <florian@margaine.com>
wrote:

> Hi,
>
> Le 31 oct. 2014 18:28, "Sherif Ramadan" <theanomaly.is@gmail.com> a =C3=
=A9crit
> :
> >
> > 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 whe=
n
> > > 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.
>
> What if there is multiple subtypes?
>
> class A extends HttpRequest {}
> class B extends HttpRequest {}
>
> What happens there?
>

As of now, all the subtypes would be called, i.e. if A has a receiveMessage
method, it would be handed the message, and if B has a receiveMessage
method it too would be handed the message. It's up to those methods to call
on subsequent parsing methods to do something with the message, obviously
any methods they don't implement are forwarded to the parent.

This clearly has some conflicts, like if default parsing is left we
overwrite superglobal variables. However, it also has benefits, in that we
can have multiple implementations for handling the request in the same code
base and it is left up to the user to decide which one to use.

So, again, this is still a draft and I'm open to suggestions about how to
handle/deal with such problems.




> > 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 no=
w
> > 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?
>
> Regards,
> Florian Margaine
>

--047d7bb047dc3bf9330506bb766f--