> On 11 Mar 2020, at 23:36, Paul M. Jones <pmjo...@pmjones.io> wrote:
>
> Hi all,
>
> Conversation on this RFC seems to have diminished. As far as I know, I have
> answered all criticisms/concerns/complaints one way or another.
>
> So if there are no more questions, and there is no objection, I will plan to
> call the vote on this proposal some time tomorrow or Friday.
>
> Thanks to everyone who has participated!
>
>
> --
> Paul M. Jones
> pmjo...@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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Hi Paul,
I appreciate what this is trying to achieve (I think - like others I’ve written
user land wrappers that achieve similar things, so having a usable
implementation in core is likely helpful), but - and I realise this is just
bike shedding - the naming seems quite odd to me.
This extension and the classes it provides are inherently about HTTP requests
made to a php ‘server’, and the response it sends back - and yet it’s called
Server{Request,Response,Buffer} etc…. The “server” part is superfluous in the
context of a php web application, because it’s all “server” side, and while
uncommon it’s not impossible to write *other* types of network server using PHP.
Cheers
Stephen
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
