这也叫适配器吗？ +适配器与装饰器
我有 2 个项目：A 和 B，它们应该相互交互。
项目A引入接口名称ISpecialTask，项目B应该实现它。
Projet B 有一个名为 TaskWithListOfProperties 的实体，该实体无法实现 ISpecialTask，因为它具有不同的属性结构（此外，所有系统都知道如何使用 TaskWithListOfProperties 并且我不想更改其结构）。
因此，我决定创建一个名为 SpecialTaskFromListOfProperties 的类，它实现 ISpecialTask 并使用 TaskWithListOfProperties 实例，以便将其用于项目之间的交互。
interface ISpecialTask {
long Id{get;}
long WorkerId{get;}
long VehicleId{get;}
long CustomerId{get;}
}
class TaskWithListOfProperties {
IDictionary<string, long> Properties {get;
}
class SpecialTaskFromListOfProperties : ISpecialTask {
public SpecialTaskFromListOfProperties(TaskWithListOfProperties ins) {
...
...
}
public long Id { get{ ... } }
public long WorkerId { get{ ... } }
public long VehicleId { get{ ... } }
public long CustomerId { get{ ... } }
}
SpecialTaskFromListOfProperties 实际上是适配器模式吗？
适配器模式和装饰器模式有什么区别？
I have 2 projects: A and B that should interactwith each other.
Project A introduce interface names ISpecialTask and Project B should implement it.
Projet B has an entity named TaskWithListOfProperties that cannot implement ISpecialTask because it has different structure of properties (in addition, all the system knows how to work with TaskWithListOfProperties and I don't want to change its structure).
So I decided to create a class named SpecialTaskFromListOfProperties that implements ISpecialTask and uses TaskWithListOfProperties instance in order to use it for the interaction between the projects.
interface ISpecialTask {
long Id{get;}
long WorkerId{get;}
long VehicleId{get;}
long CustomerId{get;}
}
class TaskWithListOfProperties {
IDictionary<string, long> Properties {get;
}
class SpecialTaskFromListOfProperties : ISpecialTask {
public SpecialTaskFromListOfProperties(TaskWithListOfProperties ins) {
...
...
}
public long Id { get{ ... } }
public long WorkerId { get{ ... } }
public long VehicleId { get{ ... } }
public long CustomerId { get{ ... } }
}
Is SpecialTaskFromListOfProperties actually the Adapter pattern?
What is the difference between the adapter pattern and decorator pattern?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
来自原始 GoF 书籍，适配器模式的意图[黑黄蜂] [Wikipedia] 是为了...
而装饰器模式的意图[Black Wasp]< /sup> [维基百科] 是...
尽管模式相似，但从定义来看，很明显这是适配器模式。您有一个方钉 (
TaskFromListOfProperties)，需要装入圆孔 (ISpecialTask)，因此您已使用SpecialTaskFromListOfProperties对其进行了调整>。装饰器将增强/扩展TaskFromListOfProperties 的现有功能，即它不会更改其现有接口。这不是
SpecialTaskFromListOfProperties正在做的事情。From the original GoF book, the intent of the Adapter pattern [Black Wasp] [Wikipedia] is to...
While the intent of the Decorator pattern [Black Wasp] [Wikipedia] is to...
Though the patterns are similar, from the definition it's clear that this is the adapter pattern. You've got a square peg (
TaskFromListOfProperties) that needs to fit into a round hole (ISpecialTask), so you've adapted it usingSpecialTaskFromListOfProperties.A decorator would augment/extend the existing functionality of
TaskFromListOfProperties, i.e. it wouldn't change its existing interface. That's not whatSpecialTaskFromListOfPropertiesis doing.取决于您实际想要实现的目标。 Adapter 和 Decorator 非常相似，但是当您实现 Adapter 时，除了转换之外，您不会带来任何新逻辑。在实现装饰器时，您实际上引入了一些以前在您正在装饰的对象中从未存在过的全新功能。
因此，长话短说，如果接口属性
Id、WorkerId等自然来自TaskWithListOfProperties- 那么您应该将其视为 适配器。否则它是一个装饰器。Depends on what you're actually trying to achieve. Adapter and Decorator are pretty much similar, however when you implement an Adapter you bring no new logic besides conversion. When implementing a Decorator you actually bring in some brand new functionality that never existed before in the object you're decorating.
So, long story short, should interface properties
Id,WorkerIdetc be naturally coming fromTaskWithListOfProperties- then you should consider it as an Adapter. Otherwise it's a Decorator.