1. “单一职责”模式
- 在软件组件的设计中,如果责任划分的不清晰,使用继承得到的结果往往是随着需求的变化,子类急剧膨胀,同时充斥着重复代码,这时候的关键是划清责任。
- 典型模式
2. Bridge 桥接模式
2.1 动机(Motivation)
- 由于某些类型的固有的实现逻辑,使得它们具有两个变化的维度,乃至多个维度的变化。
- 如何应对这种 “多维度的变化” ?如何利用面向对象技术来使得类型可以轻松地沿着两个乃至多个方向变化,而不引入额外的复杂度?
2.2 模式定义
2.3 实例代码
2.3.1 bridge1
class Messager {
public:
virtual void Login(string username, string password) = 0;
virtual void SendMessage(string message) = 0;
virtual void SendPicture(Image image) = 0;
virtual void PlaySound() = 0;
virtual void DrawShape() = 0;
virtual void WriteText() = 0;
virtual void Connect() = 0;
virtual ~Messager() {}
};
class PCMessagerBase : public Messager {
public:
virtual void PlaySound() {
}
virtual void DrawShape() {
}
virtual void WriteText() {
}
virtual void Connect() {
}
};
class MobileMessagerBase : public Messager {
public:
virtual void PlaySound() {
}
virtual void DrawShape() {
}
virtual void WriteText() {
}
virtual void Connect() {
}
};
class PCMessagerLite : public PCMessagerBase {
public:
virtual void Login(string username, string password) {
PCMessagerBase::Connect();
}
virtual void SendMessage(string message) {
PCMessagerBase::WriteText();
}
virtual void SendPicture(Image image) {
PCMessagerBase::DrawShape();
}
};
class PCMessagerPerfect : public PCMessagerBase {
public:
virtual void Login(string username, string password) {
PCMessagerBase::PlaySound();
PCMessagerBase::Connect();
}
virtual void SendMessage(string message) {
PCMessagerBase::PlaySound();
PCMessagerBase::WriteText();
}
virtual void SendPicture(Image image) {
PCMessagerBase::PlaySound();
PCMessagerBase::DrawShape();
}
};
class MobileMessagerLite : public MobileMessagerBase {
public:
virtual void Login(string username, string password) {
MobileMessagerBase::Connect();
}
virtual void SendMessage(string message) {
MobileMessagerBase::WriteText();
}
virtual void SendPicture(Image image) {
MobileMessagerBase::DrawShape();
}
};
class MobileMessagerPerfect : public MobileMessagerBase {
public:
virtual void Login(string username, string password) {
MobileMessagerBase::PlaySound();
MobileMessagerBase::Connect();
}
virtual void SendMessage(string message) {
MobileMessagerBase::PlaySound();
MobileMessagerBase::WriteText();
}
virtual void SendPicture(Image image) {
MobileMessagerBase::PlaySound();
MobileMessagerBase::DrawShape();
}
};
void Process() {
Messager *m = new MobileMessagerPerfect();
}
2.3.2 bridge2
class Messager {
protected:
MessagerImp* messagerImp;
public:
virtual void Login(string username, string password) = 0;
virtual void SendMessage(string message) = 0;
virtual void SendPicture(Image image) = 0;
virtual ~Messager() {}
};
class MessagerImp {
public:
virtual void PlaySound() = 0;
virtual void DrawShape() = 0;
virtual void WriteText() = 0;
virtual void Connect() = 0;
virtual ~MessagerImp() {}
};
class PCMessagerImp : public MessagerImp {
public:
virtual void PlaySound() {
}
virtual void DrawShape() {
}
virtual void WriteText() {
}
virtual void Connect() {
}
};
class MobileMessagerImp : public MessagerImp {
public:
virtual void PlaySound() {
}
virtual void DrawShape() {
}
virtual void WriteText() {
}
virtual void Connect() {
}
};
class MessagerLite : public Messager {
public:
MessagerLite(MessagerImp* mImp) : messagerImp(mImp) {}
virtual void Login(string username, string password) {
messagerImp->Connect();
}
virtual void SendMessage(string message) {
messagerImp->WriteText();
}
virtual void SendPicture(Image image) {
messagerImp->DrawShape();
}
};
class MessagerPerfect : public Messager {
public:
MessagerPerfect(MessagerImp* mImp) : messagerImp(mImp) {}
virtual void Login(string username, string password) {
messagerImp->PlaySound();
messagerImp->Connect();
}
virtual void SendMessage(string message) {
messagerImp->PlaySound();
messagerImp->WriteText();
}
virtual void SendPicture(Image image) {
messagerImp->PlaySound();
messagerImp->DrawShape();
}
};
void Process() {
MessagerImp* mImp = new PCMessagerImp();
Messager *m = new MessagerLite(mImp);
}
2.4 结构(Structure)

2.5 要点总结
- Bridge 模式使用 “对象间的
组合
关系” 解耦了抽象(PS:实例代码中的 Messager 类)和实现(PS:实例代码中的 MessagerImp 类)之间固有的绑定关系,使得抽象和实现可以沿着各自的维度来变化。所谓抽象和实现沿着各自维度的变化,即 “子类化” (PS:实例代码中的 MessagerLite / MessagePerfect 和 PCMessagerImp / MobileMessagerImp)它们。 - Bridge 模式有时候类似于多继承方案,但是多继承方案往往违背单一职责原则(即一个类只有一个变化的原因),复用性比较差。Bridge 模式是比多继承方案更好的解决方法。
- Bridge 模式的应用一般在 “两个非常强的变化维度”,有时一个类也有多余两个的变化维度,这时可以使用 Bridge 的扩展模式。