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:44:16 +03:00
parent cf54236bff
commit 1ef2c4beb1
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -28,10 +28,10 @@ Handling/Handler guarantee - you won't be sure that someone can process the requ
Runtime configuration risk - the order matters/and it might be that the chain is not configured correctly
Chain length/performance issues - in theory you could see a chain that is too big, and it would be a bottleneck in performance
### e. Flavors:
* Flavor 1: Execute first that matches the condition and exit -> Get one to process the request, or get the type of object
* Flavor 2: Execute all elements of chain until the condition does not match -> Execute all validators until one invalidates the request
* Flavor 3: Always execute all handlers
* Flavor 4: Instead of each handler, having a successor, you could have each handler have a list of successors, and have it's policy what handlers to execute
1. Execute first that matches the condition and exit -> Get one to process the request, or get the type of object
2. Execute all elements of chain until the condition does not match -> Execute all validators until one invalidates the request
3. Always execute all handlers
4. Instead of each handler, having a successor, you could have each handler have a list of successors, and have it's policy what handlers to execute
### f. Examples described:
* Purchase example: