Design Pattern ->Bridge

Layering & Contract Philosophy With additional indirection.

class CWindowImp
{  
    public: virtual void DrawLine(){};
        public: virtual void DrawText(){};
}
class CWindow
{
      public: virtual void DrawLine(){};
                 virtual void DrawText(){};
      protect: WindowImp* GetWindowImp()
      { 
            return WindowSystemFactory::Instance()->MakeWindwImp();
       } ;
       private: WindowImp *pWindowImp;
}
class CXPWindow: public CWindow
{
         public: void DrawLine() 
         { 
               GetWindowImp()->DrawLine();
         }
}
class CMacWindow: public CWindow
{
          public: void DrawLine() 
         { 
             do_something_special; GetWindowImp()->DrawLine();
          }
class CXPWindowImp: public CWindowImp
class CMacWindowImp: public CWindowImp

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.
• Layering or interface-Based/Oriented programming. Separate the layer.
• 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.
• Changes in the implementation of an abstraction should have no impact/effect/influence on clients; that is, their code should not have to be recompiled.
• (C++) you want to hide the implementation of an abstraction completely from clients. In C++ the representation of a class is visible in the class interface.
• You have a proliferation of classes as shown earlier in the first Motivation diagram. Such a class hierarchy indicates the need for splitting an object into two parts. Rumbaugh uses the term "nested generalizations" [RBP+91] 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 [Cop92], in which multiple objects can share the same string representation (StringRep).

Participants

• Abstraction (Window)Defines the abstraction's interface.Maintains a reference to an object of type Implementor.
• RefinedAbstraction (IconWindow)Extends the interface defined by Abstraction.
• Implementor (WindowImp)  Defines the interface for implementation classes. This interface doesn't have to correspond exactly to Abstraction's interface; in fact the two interfaces can be quite different. Typically the Implementor interface provides only primitive operations, and Abstraction defines higher-level operations based on these primitives.
• ConcreteImplementor (XWindowImp, PMWindowImp)Implements the Implementor interface and defines its concrete implementation.

Collaborations

• Abstraction forwards client requests to its Implementor object.

Consequences

The Bridge pattern has the following consequences:

• Decoupling interface and implementation. An implementation is not bound permanently to an interface. The implementation of an abstraction can be configured at run-time. It's even possible for an object to change its implementation at run-time. Decoupling Abstraction and Implementor also eliminates compile-time dependencies on the implementation. Changing an implementation class doesn't require recompiling the Abstraction class and its clients. This property is essential when you must ensure binary compatibility between different versions of a class library. Furthermore, this decoupling encourages layering that can lead to a better-structured system. The high-level part of a system only has to know about Abstraction and Implementor.
• Improved extensibility. You can extend the Abstraction and Implementor hierarchies independently.
• Hiding implementation details from clients. You can shield clients from implementation details, like the sharing of implementor objects and the accompanying reference count mechanism (if any).