> Are you saying that every PSR-7 implementation is using poor naming
conventions because they define:
Yes, I'm saying that. Furthermore, if you remember, I was trying to say
that PSR-7 is flawed from my point of view: Request/Response should be
concrete classes. There is no real place for specificity here.
But if you really insist on it, I'd call them ZendRequest, GuzzleRequest,
etc. Another way: MemoryEfficientRequest, HardCoreRfcRequest, etc. :)
> This is effectively back to using the Abstract prefix, except with a
vendor name. Is that really a win for anyone?
The thing is implementation name is not significant. You program to an
interfaces, not implementations.
On Thursday, August 18, 2016 at 5:04:33 PM UTC+3, Woody Gilk wrote:
>
>
>
> On Thursday, August 18, 2016 at 3:31:16 AM UTC-5, Daniel Plainview wrote:
>>
>> Also, you wouldn't be allowed to have poor naming like Foo implements
>> FooInterface. It looks like naming impotence: you have implementation, why
>> you can't describe what makes this implementation specific: MySqlFoo?
>> MemcachedFoo? ZendFoo?
>>
>
> Are you saying that every PSR-7 implementation is using poor naming
> conventions because they define:
>
> class Request implements RequestInterface { ... }
>
> It sure seems like it. What should these be named? GuzzleRequest,
> DiactorosRequest? So then we'd have:
>
> namespace Zend\Diactoros;
>
> use Psr\Http\Request;
>
> class DiactorosRequest implements Request { ... }
>
> This is effectively back to using the Abstract prefix, except with a
> vendor name. Is that really a win for anyone?
>
--
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 php-fig+unsubscr...@googlegroups.com.
To post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/php-fig/d3e6bbbc-c8a9-4c02-87b4-2c6e85824e64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
