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

Leave a blank line before examples described

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-12 12:55:22 +03:00
parent ca20391c15
commit a63c77153f
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@@ -27,6 +27,7 @@ Chain length/performance issues - in theory you could see a chain that is too bi
* Flavor 2: Execute all elements of chain until the condition does not match -> Execute all validators until one invalidates the request * 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 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 * 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
### e. Examples described: ### e. Examples described:
* Purchase example: * Purchase example:
Starting class: PurchaseExample.CheckAuthority Starting class: PurchaseExample.CheckAuthority