Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108453 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 67341 invoked from network); 11 Feb 2020 11:20:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Feb 2020 11:20:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1866E180211 for ; Tue, 11 Feb 2020 01:34:05 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_40, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS12306 82.98.64.0/18 X-Spam-Virus: No X-Envelope-From: Received: from fra.ammma.de (fra.ammma.de [82.98.68.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 11 Feb 2020 01:34:04 -0800 (PST) Received: from ammma.de (fra2-hb [192.168.1.12]) by fra.ammma.de (Postfix) with ESMTPS id 8118C5B02C6 for ; Tue, 11 Feb 2020 10:33:54 +0100 (CET) Received: from mail.ammma.net ([192.168.110.0]) by ammma.de (8.11.6/8.11.6/AMMMa AG) with ESMTP id 01B9XrY16944 for ; Tue, 11 Feb 2020 10:33:53 +0100 Received: from neo (unknown [192.168.110.0]) by mail.ammma.net (Postfix) with ESMTPS id 3956F4AE10 for ; Tue, 11 Feb 2020 10:34:02 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by neo (Postfix) with ESMTP id AEA2219077F7 for ; Tue, 11 Feb 2020 10:34:01 +0100 (CET) Received: from neo ([IPv6:::1]) by localhost (neo.fritz.box [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id GVk9gJkZysCK for ; Tue, 11 Feb 2020 10:33:58 +0100 (CET) Received: from neo (localhost [IPv6:::1]) by neo (Postfix) with ESMTPS id E014B1907671 for ; Tue, 11 Feb 2020 10:33:57 +0100 (CET) Received: from internbi.hdnet.de (internbi.hdnet.de [87.138.198.64]) by yunosh.horde.org (Horde Framework) with HTTPS; Tue, 11 Feb 2020 09:33:57 +0000 Date: Tue, 11 Feb 2020 09:33:57 +0000 Message-ID: <20200211093357.Horde.rLSaCIKR44fKvPJyltsdQC_@yunosh.horde.org> To: internals@lists.php.net In-Reply-To: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> User-Agent: Internet Messaging Program (IMP) H6 (7.0.0-git) Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2) From: jan@horde.org (Jan Schneider) References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> Zitat von Paul M. Jones : > Hi Internals, > > After a couple of years of incubation, I am happy to offer a second > version of this RFC: > > https://wiki.php.net/rfc/request_response > > It proposes an object-oriented approach around request and response > functionality already existing in PHP, in order to reduce the > global-state problems that come with superglobals and the various > response-related functions. I like this proposal a lot, since it provides a clear, concise interface to these commonly uses, yet inconveniant to use, existing functions and variables without having to always use a full-featured userland library. Speaking of interfaces: since you suggest using decoration and composition over extension for ServerResponse, I am missing a ServerResponseInterface, so that you can easily typehint such userland decorators. -- Jan Schneider The Horde Project https://www.horde.org/