From 216428eb5c49bf260b327225c6f6970ae941c023 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ilkka=20Sepp=C3=A4l=C3=A4?= Date: Mon, 27 May 2024 12:08:46 +0300 Subject: [PATCH] docs: update servant --- servant/README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/servant/README.md b/servant/README.md index 992816903..8927f3a65 100644 --- a/servant/README.md +++ b/servant/README.md @@ -128,10 +128,6 @@ Running the application produces: In this example, the `Servant` class provides services to the `Royalty` objects. The `Servant` class doesn't know about the specific implementation of the `Royalty` objects, it only knows that it can provide certain services to them. This is a good example of the Servant design pattern. -## Class diagram - -![Servant](./etc/servant-pattern.png "Servant") - ## Applicability * Use the Servant pattern when you need to provide a common functionality to a group of classes without polluting their class definitions. @@ -167,4 +163,3 @@ Trade-offs: * [Design Patterns: Elements of Reusable Object-Oriented Software](https://amzn.to/3w0pvKI) * [Java Design Patterns: A Hands-On Experience with Real-World Examples](https://amzn.to/3yhh525) * [Pattern-Oriented Software Architecture Volume 1: A System of Patterns](https://amzn.to/3xZ1ELU) -* [Let's Modify the Objects-First Approach into Design-Patterns-First](http://edu.pecinovsky.cz/papers/2006_ITiCSE_Design_Patterns_First.pdf)