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

Update readme

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-12 13:40:41 +03:00
parent af4a7f49bf
commit 9c6d0169f0
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -8,15 +8,15 @@ Implemented in project: ChainOfResponsibility
### a. Pattern description:
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)
### b.When using the Chain of Responsibility is more effective:
More than one object can handle a command
The handler is not known in advance
The handler should be determined automatically
It<EFBFBD>s wished that the request is addressed to a group of objects without explicitly specifying its receiver
The group of objects that may handle the command must be specified in a dynamic way.
Examples in real life:
* -java.util.logging.Logger.#log()
* -javax.servlet.Filter#doFilter()
* -Spring Security Filter Chain
* More than one object can handle a command
* The handler is not known in advance
* The handler should be determined automatically
* It<EFBFBD>s wished that the request is addressed to a group of objects without explicitly specifying its receiver
* The group of objects that may handle the command must be specified in a dynamic way.
* Examples in real life:
* -java.util.logging.Logger.#log()
* -javax.servlet.Filter#doFilter()
* -Spring Security Filter Chain
### c. Actors
* Client - creates the chain, and invokes the first handler