Hi Stephen,
> On Mar 13, 2020, at 02:41, Stephen Reay <php-li...@koalephant.com> wrote:
>
> 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.
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!
--
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
