文章目录

  • ​​1.“单一职责”模式:​​
  • ​​2.动机(Motivation)​​
  • ​​3.原始案例​​
  • ​​4.结构(Structure)​​
  • ​​5.要点总结​​

1.“单一职责”模式:

在软件组件的设计中,如果责任划分的不清晰,使用继承得到的结果往往是随着需求的变化,子类极具膨胀,同时充斥着重复代码,这时候的关键时划清责任。
典型模式

  • Decorator
  • Bridge

2.动机(Motivation)

由于某些类型的固有的实现逻辑,使得它们具有两个变化的维度,乃至多个纬度的变化。

如何应对这种“多维度的变化”?如何利用面向对象技术来使得类型可以轻松地沿着两个乃至多个方向变化,而不引入额外的复杂度?

3.原始案例

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() {
//==============
}
};

//业务抽象:m
//类的数目:1+n+n*m个类

//业务抽象
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();
}

改良案例
Messager承载了过多的功能,平台实现和业务抽象。两个不同的变化方向,带动了类实现方向不同。应该分到不同的类中。

class Messager {
protected:
MessagerImp* messagerImp;
Messager(MessagerImp* mImp) :messagerImp(mImp) {

}
public:
virtual void Login(string username, string password) = 0;
virtual void SendMessage(string message) = 0;
virtual void SendPicture(Image image) = 0;
;
virtual ~Messager();
};
//平台实现Imp
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() {
//==============
}
};

//业务抽象:m
//类的数目:1+n+m个类
//业务抽象
class MessagerLite : public Messager {
MessagerLite(MessagerImp* msg): Messager(msg) {

}
public:
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 {
MessagerPerfect(MessagerImp* msg) :Messager(msg) {

}

public:
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 Messager(mImp);
}

4.结构(Structure)

  • 红色圈是稳定的基类,Abstraction就是Messager(业务),Implementor就是MessagerImp(平台),Messager中有个指针指向MessagerImp,
  • 蓝色圈是变化的,RefindAbstraction是MessagerLite,MessagerPerfect,ConcreteImplementorA是PCMessagerImp,MobileMessagerImp

5.要点总结

Bridge模式使用“对象间的组合关系”解耦了抽象和实现之间固有的绑定关系,使得抽象和实现可以沿着各自的维度来变化。所谓抽象和实现沿着各自纬度的变化,即“子类化”它们。

Bridge模式有时候类似于多继承方案,但是多继承方案往往违背 单一职责原则(即一个类只有一个变化的原因),复用性比较差。Bridge模式是比多继承方案更好的解决方法。

Bridge模式的应用一般在“两个非常强的变化维度”,有时一个 类也有多于两个的变化维度,这时可以使用Bridge的扩展模式。