Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78533 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38699 invoked from network); 31 Oct 2014 20:16:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Oct 2014 20:16:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=willfitch@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=willfitch@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 66.111.4.27 as permitted sender) X-PHP-List-Original-Sender: willfitch@php.net X-Host-Fingerprint: 66.111.4.27 out3-smtp.messagingengine.com Received: from [66.111.4.27] ([66.111.4.27:47475] helo=out3-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/5B-15608-11EE3545 for ; Fri, 31 Oct 2014 15:16:18 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A009120872 for ; Fri, 31 Oct 2014 16:16:15 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 31 Oct 2014 16:16:15 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=W+ozwurWHpUPOz2Y3fWJbon /VU8=; b=nUHXN+i4v58nwlWs+Rzqb4LmuB4fhxqEkFXht9jx+6tcPOxr7l++G+t 3/sgg+JvWXN3KFBcuCCuQo4yKSKHGa0k0Y4MPD0snYkjmrxdYa2sAozWuRxjfpUJ EOSea2LvzezETKVea2c2htfCdu4c7mL4OYXtbvMOQdQoxfo8YlaI= X-Sasl-enc: Ztw+fRoZEB8H00SgZty5JpKnkZm5ELtDlvmb39HrWe1z 1414786575 Received: from wills-mbp.home (unknown [173.59.114.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 50B12C00008; Fri, 31 Oct 2014 16:16:15 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) In-Reply-To: Date: Fri, 31 Oct 2014 16:16:14 -0400 Cc: Rowan Collins , PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <5452B87B.5040009@garfieldtech.com> <0B797CE3-7AFA-4330-9A98-D3CAFC6D6072@ajf.me> <5453B114.6050400@gmail.com> <5453C250.8090803@gmail.com> <5453D6D5.2070705@garfieldtech.com> <5453E492.6020304@gmail.com> To: Sherif Ramadan X-Mailer: Apple Mail (2.1990.1) Subject: Re: [PHP-DEV] New Standardized HTTP Interface From: willfitch@php.net (Will Fitch) > On Oct 31, 2014, at 4:05 PM, Sherif Ramadan = wrote: >=20 > On Fri, Oct 31, 2014 at 3:35 PM, Rowan Collins = > wrote: >=20 >> Sherif Ramadan wrote on 31/10/2014 18:52: >>=20 >>> 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. >>>=20 >>=20 >> The decision about *whether this is needed in core* is not something = you >> can ignore by saying "this is about core". The fact that PHP-FIG is = working >> on something very closely related to this makes a difference to that >> question, and pretending that's irrelevant is not constructive. >>=20 >>=20 > First of all, I'm not ignoring anything. I very much appreciate all of = your > input. However, reiterating what you've already said with every single = one > of your responses attempting to derail this discussion into a matter = that > concerns FIG or PSR or whatever other third party concern that is > tangentially related to the word HTTP is something I will not stand = for. While not too specific to Rowan, reiterating the pecl/http approach is = indirectly what your asking for? I have mentioned this numerous times, = but you haven=E2=80=99t responded with a reason not to take this = approach - which is an RFC that was presented for discussion prior to = yours. Forgetting about FIG or PSR, if pecl/http v2 made it into = core/ext, would this not satisfy your concerns described in your RFC and = conversations? We=E2=80=99re spinning wheels here, and so many, mostly core developers, = have been reiterating the resistance to superglobals, and rightfully so. = I would suggest either concentrating the efforts you=E2=80=99re trying = here towards existing efforts (pecl/http), or present a better approach. >=20 > I read what you've had to say about FIG and PSR and I'm taking it into > consideration. That doesn't mean I have to yield to your preference. = Nor > does that mean this RFC has now become irrelevant because somewhere on > planet earth someone has come up with a competing idea/concept. I = welcome > competition. That is only beneficial to PHP. >=20 > If you would like to further this discussion beyond reiterating the = words > PSR and FIG then please explain to me how what you're talking about = solves > any of the problems I'm attempting to solve with this RFC? Namely, how = does > this PSR solve the problem that PHP will not populate $_FILES or = $_POST if > a multipart PUT request is sent to PHP? Pointing out specifics, using > references, and providing any additional examples/documentation is = more > than welcome if it will help me improve this RFC (but only if it is = geared > toward the same goals that this RFC has). >=20 > Thanks