Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108438 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41421 invoked from network); 10 Feb 2020 18:48:20 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 10 Feb 2020 18:48:20 -0000 To: internals@lists.php.net References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> Date: Mon, 10 Feb 2020 17:02:02 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.8.17.105 Subject: Re: RFC: Server-Side Request and Response Objects (v2) From: marandall@php.net (Mark Randall) Message-ID: On 10/02/2020 16:18, Paul M. Jones wrote: > Hi Internals, > Thanks in advance for your time and consideration while evaluating it. I suspect this is a similar sentinment to the previous version, but I can personally see no major benefit to having this as a core extension. I think the reality is that discussing it "on its own merits" is to completely ignore the wider ecosystem that already performs these functions, with more capabilities, and with potentially hundreds of thousands of implementations already in place. Does it add capabilities which cannot exist in userland or cannot exist in a reasonably performant way? Doesn't seem so except for a readonly property. If not, leave it to userland. Mark Randall