anchor.diff:  [NOTE]
   This section contains Pedestal's router reference which modified a little bit based on *HellHound* requirements.
   
  -HellHound uses `Pedestal Router` for HTTP routing
  +HellHound uses `Pedestal Router` for HTTP routing, So everything you read in this section is applicable to
  +your HellHound application as well.
   
   === Routes vs. Routers
   
  
positive.code: |===
  | Router | Performance | Scaling in # Routes | Limitations
  
  |Map Tree (default after 0.5.2)
  | Very fast
  | Constant
  | Applies when all routes are static. Falls back to prefix tree if any routes have path parameters or wildcards.
  
  |Prefix Tree (default prior to 0.5.2)
  | High performance, space efficient
  | Log32(N)
  | Wildcard routes always win over explicit paths in the same subtree. E.g., `/path/:wild` will always match, even if `/path/user` is defined
  
negative.code: 
  === Table Syntax
  
  Table syntax is expanded by
  link:http://pedestal.io/api/pedestal.route/io.pedestal.http.route.html#var-expand-routes[`expand-routes`]
  into the full (verbose) syntax shown above.
  
  When the argument to
  link:http://pedestal.io/api/pedestal.route/io.pedestal.http.route.html#var-expand-routes[`expand-routes`]
  is a *set*, it will be expanded using the table syntax.
  
  In table syntax, each route is a vector of:
  