----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]>
The delegators make it easier to perform the lifecycle management once the component has been properly "parsed". This allows the developer the most freedom possible including coding with method names in their native tongue (I used Spanish above because I can at least know a couple words in that language).
Nonsense. I'm from Brazil and I don't see any advantage of use portuguese to name my methods. Everything else is in english, why my service ou configure methods should be in portuguese? More: using attributes to define the "role" or dependency is fine, but use it to define lifecycle method is a bad idea. This would requires a lot of attributes checking through reflection resulting - at least - in a poor performance. My opnion: interfaces are just fine.
Seems to me that everyones who start a project in .net wants to use attributes to everything. I used to do that... :-)
my two cents.
Well said. WIth that argument, let's put the interfaces back in.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
