Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78489 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14885 invoked from network); 30 Oct 2014 20:42:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Oct 2014 20:42:29 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.245 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 198.187.29.245 imap11-3.ox.privateemail.com Received: from [198.187.29.245] ([198.187.29.245:42317] helo=imap11-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/42-04091-4B2A2545 for ; Thu, 30 Oct 2014 15:42:28 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id CF0E98800F7; Thu, 30 Oct 2014 16:42:25 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qco1x679x4b8; Thu, 30 Oct 2014 16:42:25 -0400 (EDT) Received: from oa-res-26-28.wireless.abdn.ac.uk (oa-res-26-28.wireless.abdn.ac.uk [137.50.26.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id CF7728800E7; Thu, 30 Oct 2014 16:42:24 -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: Thu, 30 Oct 2014 20:42:22 +0000 Cc: Florian Margaine , PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <36B5E957-01C0-40F2-B4CE-5B02D11ACA14@ajf.me> To: Sherif Ramadan X-Mailer: Apple Mail (2.1990.1) Subject: Re: [PHP-DEV] New Standardized HTTP Interface From: ajf@ajf.me (Andrea Faulds) > On 30 Oct 2014, at 20:33, Sherif Ramadan = wrote: >=20 > Yes, this proposal is intended to do two things. 1) Fix the = aforementioned problems. By the sounds of things, it doesn=E2=80=99t fix these problems, it just = adds a new interface which lacks them. That=E2=80=99s not the same = thing. > 2) Improve upon the capabilities of PHP's request handling for future = use cases through a unified interface. What unified interface? You=E2=80=99re allowing anyone and everyone to = implement their own request handling. > If you consider all of the major existing PHP frameworks today there = is always some form of HttpRequest class handling these things and = almost all of them do it slightly differently. What's worse, is they are = all very inefficient implementations that I believe can be done far more = efficiently in php-src. A lost of them are also unnecessarily complex. I = think all of this can be simplified if the interface is just laid out in = a straight-forward manner and then userland implementations will find = less and less reason to over-engineer the implementation. The only reason an implementation of HttpRequest would be inefficient is = because it has to work-around problems with $_GET and $_POST. Problems = we could simply fix. -- Andrea Faulds http://ajf.me/