anchor.diff:  * They can provide access to other resources, such as database connection pools.
   
   Argument resolver functions can be specified as metadata directly on the resource handler function;
  -the +:argument-resolvers+ metadata key is a sequence of resolvers.
  +the +:arg-resolvers+ metadata is a sequence of resolvers.
   
   Argument resolver functions take precedence over the default argument resolvers.
   
  
positive.code: 
  A typical web service will expose some number of resources; under Ring this means mapping a number of namespaces.
  
  The +namespace-handler+ function is the easy way to do this mapping. It combines +compojure.core/context+ with Rook's
  +namespace-middleware+ (which identifies the function to be invoked within the namespace) and +default-rook-pipeline+ (which resolves
  arguments and invokes the identified function).
  
  ----
  (routes
  
negative.code: 
  * Finally, unmatched arguments simply default to +nil+.
  
  Argument resolution is performed by the {api}/io.aviso.rook.html#var-rook-dispatcher[+rook-dispatcher]+ function,
  just before invoking the resource handler function.
  The {api}/io.aviso.rook.html#var-default-rook-pipeline[+default-rook-pipeline+] includes +rook-dispatcher+ plus middleware to add any argument resolvers from the
  function's +:arg-resolvers+ metadata footnote:[Remember that Rook merges function metadata with metadata of the containing namespace]
  to the list of argument resolvers used by +rook-dispatcher+.
  
  