Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    Thanks Yanis. This may be an implementation in decorator pattern. Actually my point was do we really need to make the decorator as abstract class ? Commented Nov 22, 2013 at 15:48
  • @TechJay I made an explanation, I hope it make sense. Commented Nov 23, 2013 at 21:17
  • as per your comment, i think if we use the interfaces and DI, there won't be any redundant code. We just need to pass the appropriate dependency using interfaces container. Commented Nov 26, 2013 at 14:49
  • @TechJay As I told you it's not necessary, but it's consider best practice therefor it's a design pattern. If you have one model there isn't a big deal. But if you have a lot and many methods too implement an abstract class becomes handy. What DI stands for? Dependency injection? Commented Nov 26, 2013 at 17:27