From ca20391c1516e50a5e63ea2b2d82dc106e599756 Mon Sep 17 00:00:00 2001 From: Petrutiu Mihai Date: Tue, 12 Jul 2016 12:53:23 +0300 Subject: [PATCH] Update readme --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 91d30ba..1ab862a 100644 --- a/README.md +++ b/README.md @@ -23,10 +23,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 ### d. 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 +* 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 ### e. Examples described: * Purchase example: Starting class: PurchaseExample.CheckAuthority