Gardient/behavioral-patterns
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-14 14:22:22 +03:00
committed by GitHub
parent 0b0264561e
commit f1e170a467
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -41,7 +41,18 @@ Patterns described:
--------------------------- ---------------------------
Implemented in project: ChainOfResponsibility Implemented in project: ChainOfResponsibility
### a. Pattern description: ### a. Pattern description:
[ChainOfResponsibilityClassDiagram]: https://github.com/MihaiTheCoder/BehavioralPatterns/blob/master/BehavioralPatternsDiagrams/ChainOfResponsibility/ChainOfResponsibilityClassDiagram.PNG "Chain of responsibility class diagram"
[ChainOfResponsibilitySequenceDiagram]: https://github.com/MihaiTheCoder/BehavioralPatterns/blob/master/BehavioralPatternsDiagrams/ChainOfResponsibility/ChainOfResponsibilitySequenceDiagram.PNG "Chain of responsibility sequence diagram"
Decouples sender and receiver (as a sender you don't know who will handle the request/ as a receiver you don't know who the sender is necessary) Decouples sender and receiver (as a sender you don't know who will handle the request/ as a receiver you don't know who the sender is necessary)
Class diagram:
![alt text][ChainOfResponsibilityClassDiagram]
Sequence diagram:
![alt text][ChainOfResponsibilitySequenceDiagram]
### b.When using the Chain of Responsibility is more effective: ### b.When using the Chain of Responsibility is more effective:
* More than one object can handle a command * More than one object can handle a command
* The handler is not known in advance * The handler is not known in advance