Description: * Coupling between classes and class libraries is a major maintenance
* headache. To ease this problem, often the client talks to an
* abstraction description, which in turn calls an implementation.
* Sometimes these must evolve- when one changes there can be a need
* to change the other. The bridge design pattern lets the abstraction
* and its implementation evolve separately.
*
* So, what is the difference between a bridge and an interface? Interfaces
* can be used when creating bridges- but it should be noted that bridges
* have additional possibilities. Both the abstraction and the
* implementation may evolve over time and be the parent of derived classes.
* The operations needed in the implementation could be defined in an
* interface if there are no standard methods which are available at the
* top-level of the implementation.
*
*/
To Search:
File list (Check if you may need any files):
adapter_designpattern.txt
Download