HttpRequest is not good name, because Request from PSR-7 is already HTTP-request.
However, when I asked community about lack of different implementations, Matthew Weier O'Phinney said the following ( https://groups.google.com/forum/#!topic/php-fig/RQuMBMD48zU): > Guzzle has traditionally focused on client behavior, and has optimizations around memory usage and generator driven streams; streams are its particular strength > Diactoros and Slim focus on server side details, with the former being a full, general purpose implementation If these implementations are truly different, I don't understand why they can't reflect it in the name (thanks to Matthew): ClientFocusedRequest, ServerSideFocusedRequest, MemoryEfficientRequest, FullRfcCompatibleRequest, etc. If they are not truly different, why do you need the interface at all? You either have *different* implementation or you have the only one, as simple as that. On Thursday, August 18, 2016 at 5:46:21 PM UTC+3, Woody Gilk wrote: > > > On Thu, Aug 18, 2016 at 9:24 AM, Erik Landvall <[email protected] > <javascript:>> wrote: > >> @Woody | It depends on what type of request it is. The implementation IMO >> could be called `HttpRequest`. But others may have internal and external >> requests.. eg. InternalRequest and ExternalRequest. > > > That's just replacing a suffix with a prefix. Zero sum game. > > -- > Woody Gilk > http://about.me/shadowhand > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/26e9735e-e9a8-4399-aa42-a56deb10298e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
