Update readme

This commit is contained in:
Petrutiu Mihai
2016-07-12 13:39:16 +03:00
parent 465ed40bc5
commit 14bd8fa4d1

View File

@@ -7,7 +7,6 @@ Patterns described:
Implemented in project: ChainOfResponsibility Implemented in project: ChainOfResponsibility
### a. Pattern description: ### 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) 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)
Hierarchical in nature
### 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
@@ -15,9 +14,9 @@ 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 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. The group of objects that may handle the command must be specified in a dynamic way.
Examples in real life: Examples in real life:
-java.util.logging.Logger.#log() * -java.util.logging.Logger.#log()
-javax.servlet.Filter#doFilter() * -javax.servlet.Filter#doFilter()
-Spring Security Filter Chain * -Spring Security Filter Chain
### c. Actors ### c. Actors
* Client - creates the chain, and invokes the first handler * Client - creates the chain, and invokes the first handler
* Handler - defines an interface for handling the requests, optional to set the succesor * Handler - defines an interface for handling the requests, optional to set the succesor