> > That's just replacing a suffix with a prefix. Zero sum game. >
@Woody, thanks for your response. I understand that you don't see the difference in describing the request as what sort of Request it is. Correct me if I misunderstood you. I will try to explain why there is a difference to me. Lets say that you make an implementation and simply name it `Request`. Some time go by and you now need to make a new implementation in your project for the web socket protocol. Now you have an implementation named `Request` and one called, example: `WsRequest`. What makes your first implementation so generic in this case? it's just an implementation of a Request (not a request interface - the implementation part already covered that part). Instead I would say that it makes better sense to describe your requests after what sort of request it is, eg `HttpRequest` and `WsRequest` and simply let them implement a `Request` that defines the aggregation. [sarcasm]Or we can suffix every implementation with the `Class` keyword, and every function with the `Function` keyword, and every integer with the `Integer` keyword and every constant with the `Const` keyword...[/sarcasm] ...this sarcasm is meant to make a point how I see the suffix as redundant by associating it to a common ground. I also noticed that this is an internal discussion, so I will stop posting here after this. I don't really understand why it's internal though? -- 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/CACLFiRAehtT0SQoh5exKzRKaLWL%3DVn__VTqucswy5-NaY_yPjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
