Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109000 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48189 invoked from network); 13 Mar 2020 15:18:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 13 Mar 2020 15:18:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B70501804C6 for ; Fri, 13 Mar 2020 06:40:00 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS29169 217.70.176.0/20 X-Spam-Virus: No X-Envelope-From: Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 13 Mar 2020 06:39:59 -0700 (PDT) X-Originating-IP: 107.223.28.39 Received: from samurai.attlocal.net (107-223-28-39.lightspeed.nsvltn.sbcglobal.net [107.223.28.39]) (Authenticated sender: pmjones@pmjones.io) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 07235C000A; Fri, 13 Mar 2020 13:39:56 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) In-Reply-To: Date: Fri, 13 Mar 2020 08:39:54 -0500 Cc: PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: <0B40E6E5-342F-4D81-9CAA-A0C0739A7718@pmjones.io> References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> To: Stephen Reay X-Mailer: Apple Mail (2.3608.60.0.2.5) Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2) From: pmjones@pmjones.io ("Paul M. Jones") Hi Stephen, > On Mar 13, 2020, at 02:41, Stephen Reay = wrote: >=20 > I realise this is just bike shedding - the naming seems quite odd to = me. >=20 > This extension and the classes it provides are inherently about HTTP = requests made to a php =E2=80=98server=E2=80=99, and the response it = sends back - and yet it=E2=80=99s called Server{Request,Response,Buffer} = etc=E2=80=A6. The =E2=80=9Cserver=E2=80=9D part is superfluous in the = context of a php web application, because it=E2=80=99s all =E2=80=9Cserver= =E2=80=9D side, and while uncommon it=E2=80=99s not impossible to write = *other* types of network server using PHP. I share your feeling here, and I don't think it's bike shedding. The = naming is still an open question on the RFC. I mentioned some other candidate names here ... https://externals.io/message/108436#108702 ... and re-reading your comment above, it looks like you saw that one. Do you have alternative suggestions or preferences on the names? Or, do = you feel that "Request" and "Response" and "ResponseSender" (without any = prefixes at all) would be sufficiently obvious? Let me know, and thanks for bringing it up! --=20 Paul M. Jones pmjones@pmjones.io http://paul-m-jones.com Modernizing Legacy Applications in PHP https://leanpub.com/mlaphp Solving the N+1 Problem in PHP https://leanpub.com/sn1php