Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109180
Date: Sat, 21 Mar 2020 19:54:03 +0300 (EET)
Reply-To: "Ekin B." <me@ekins.space>
To: Mark Randall <marandall@php.net>, internals@lists.php.net
Message-ID: <1927664226.18302.1584809643504@privateemail.com>
References: <8B8A570A-545C-4CBF-9145-C9FC0B0E2AA1@pmjones.io>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Importance: Normal
Subject: Re: [PHP-DEV] Re: [VOTE] Server-Side Request and Response Objects
 (v2)
From: me@ekins.space ("Ekin B.")

Hi,

> On March 20, 2020 5:35 PM Mark Randall <marandall@php.net> wrote:
> 
>  
> On 20/03/2020 13:31, Paul M. Jones wrote:
> > I have opened the vote on Server-Side Request and Response Objects at <https://wiki.php.net/rfc/request_response>.
> To practice what I preach:
> 
> I have voted against, as I don't believe this proposal offers anything 
> which isn't already possible using much more comprehensive and 
> well-supported userland libraries.
> 
> At best, adding in yet another mechanism risks further fragmenting the 
> ecosystem to the major detriment of ecosystem interoperability.
> 
> This RFC should be revisited if PHP ever gets native support for 
> long-running multi-request processes, as at that time there would be a 
> clear need for a self-contained request-specific request / response object.
> 
> Mark Randall
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php

First of all I'd like to thank you for all the efforts put into the RFC! I noticed I haven't when I opined before.

I've voted against for pretty much the same reasons Mark mentioned above.

Best,
Ekin H. Bayar
https://ekins.space 
https://heap.space