Using the Decorator Design Pattern to Address Cross-Cutting Concerns
•
1 like•1,256 views
Presented 2013-07-15 to the VT .NET user group
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Using the Decorator Design Pattern to Address Cross-Cutting Concerns
- 1. Rob Hale VT .NET User Group July 15, 2013
- 2. Common functionality that spans layers and tiers. Examples are operations like: authentication authorization caching communication exception management validation logging
- 4. Every class should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility. A responsibility is a reason to change, and a class or module should have one, and only one, reason to change.
- 5. public void Execute() { Logger.Info("Starting execution"); Console.WriteLine("We're doing our job!"); Logger.Info("Done execution"); } Two responsibilities: Logging Processing
- 7. The good news Processor is more loosely coupled The bad news Processor still has two responsibilities
- 8. IComponent + Operation() ConcreteComponent + Operation() Decorator - iComponent + Operation() ConcreteDecorator - iComponent + Operation()
- 10. http://www.dofactory.com/Patterns/PatternD ecorator.aspx ◦ Check out the “real world” example