Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78524 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17008 invoked from network); 31 Oct 2014 17:32:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Oct 2014 17:32:23 -0000 Authentication-Results: pb1.pair.com header.from=florian@margaine.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=florian@margaine.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain margaine.com from 209.85.223.182 cause and error) X-PHP-List-Original-Sender: florian@margaine.com X-Host-Fingerprint: 209.85.223.182 mail-ie0-f182.google.com Received: from [209.85.223.182] ([209.85.223.182:49540] helo=mail-ie0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A6/57-15608-4A7C3545 for ; Fri, 31 Oct 2014 12:32:22 -0500 Received: by mail-ie0-f182.google.com with SMTP id rd18so1718057iec.41 for ; Fri, 31 Oct 2014 10:32:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=scdg6MGJ8C0Qosm/jTEJcvC8g6/xQx3iCz1+/pmxAYk=; b=fnUPGiwDByv9dEKSupefXoNOrwC0NSkH6CtA3Rw29fGp3OABvQrUDAHdaI/RkM77U5 k+vrIa/1qUR8pjaU6T9TlG0KMwD0W5IuzwJFEBtE14lghLa00CLifRRW22L3LuQhOR2S 28DUOWK429GuxeuD0lBcG23KFOD/QvElQgeGvV6O1bZj9k6qq+Mq8lwGmOLxRBKm/DJ8 ARVv7ab9K9MdjfaLMm0MNOlIBfuBKYWrsPCF5/AH2XLJBx0bmZjNUiWSWSFWgMn5e3Wi QDZ5pf+vRTvtNgVoirykUkSw9W/LaJIE+6l/SeQTAg+jFdFdyy1l1YfPEy+EgonNutom fceA== X-Gm-Message-State: ALoCoQn2DwcwApIxo7VTo8pxNbQWhNrePbwj4MTMGpVK3tjP933uDEEy3qUEIdcogpq5xm8ibONo MIME-Version: 1.0 X-Received: by 10.51.17.2 with SMTP id ga2mr5926118igd.38.1414776738487; Fri, 31 Oct 2014 10:32:18 -0700 (PDT) Received: by 10.107.25.200 with HTTP; Fri, 31 Oct 2014 10:32:18 -0700 (PDT) X-Originating-IP: [80.215.229.197] Received: by 10.107.25.200 with HTTP; Fri, 31 Oct 2014 10:32:18 -0700 (PDT) In-Reply-To: References: <5452B87B.5040009@garfieldtech.com> <0B797CE3-7AFA-4330-9A98-D3CAFC6D6072@ajf.me> <5453B114.6050400@gmail.com> <5453C250.8090803@gmail.com> Date: Fri, 31 Oct 2014 18:32:18 +0100 Message-ID: To: Sherif Ramadan Cc: PHP Internals , Rowan Collins Content-Type: multipart/alternative; boundary=001a113491e4ef3e270506bb60c0 Subject: Re: [PHP-DEV] New Standardized HTTP Interface From: florian@margaine.com (Florian Margaine) --001a113491e4ef3e270506bb60c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Le 31 oct. 2014 18:28, "Sherif Ramadan" a =C3=A9c= rit : > > On Fri, Oct 31, 2014 at 1:09 PM, Rowan Collins > 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. What if there is multiple subtypes? class A extends HttpRequest {} class B extends HttpRequest {} What happens there? > 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? Regards, Florian Margaine --001a113491e4ef3e270506bb60c0--