gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

#354 Add maven model for feature toggle design pattern

Browse Source
This commit is contained in:
Joseph McCarthy
2016-01-25 21:14:24 +00:00
parent cf10bd1d05
commit d7526fc7c0
86 changed files with 1165 additions and 270 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
bridge/index.md
View File

@@ -10,15 +10,17 @@ tags:
- Difficulty-Intermediate
---
**Also known as:** Handle/Body
## Also known as
Handle/Body
**Intent:** Decouple an abstraction from its implementation so that the two can
## Intent
Decouple an abstraction from its implementation so that the two can
vary independently.
![alt text](./etc/bridge.png "Bridge")
**Applicability:** Use the Bridge pattern when
## Applicability
Use the Bridge pattern when
* you want to avoid a permanent binding between an abstraction and its implementation. This might be the case, for example, when the implementation must be selected or switched at run-time.
* both the abstractions and their implementations should be extensible by subclassing. In this case, the Bridge pattern lets you combine the different abstractions and implementations and extend them independently
@@ -26,6 +28,6 @@ vary independently.
* you have a proliferation of classes. Such a class hierarchy indicates the need for splitting an object into two parts. Rumbaugh uses the term "nested generalizations" to refer to such class hierarchies
* you want to share an implementation among multiple objects (perhaps using reference counting), and this fact should be hidden from the client. A simple example is Coplien's String class, in which multiple objects can share the same string representation.
**Credits**
## Credits
* [Design Patterns: Elements of Reusable Object-Oriented Software](http://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612)