anchor.diff:  
   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).
  +The {api}/io.aviso.rook.html#var-namespace-handler[+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+.
   
   ----
   (routes
  
positive.code: WARNING: Currently, general argument resolvers are invoked _first_, before function-specific resolvers; this seems backwards
  and is likely to change.
  
  Function +arg-resolver-middleware+ is used to specify additional functions for +:arg-resolvers+.
  
  Function +build-map-arg-resolver+ constructs an argument resolver function from a map; It simply returns values from
  the map.
  
  Function +build-fn-arg-resolver+ constructs an argument resolver function from a map of _functions_; The functions
  are selected by the argument keyword, and passed the request.
  
  TIP: Remember that a keyword can act like a function when passed a map, such as the Ring request.
  
  Function +request-arg-resolver+ is an argument resolver that resolves the argument keyword against the Ring request map itself.
  
  +arg-resolver-middleware+ accepts any number of argument resolvers, allowing them to be easily composed and
  contributed:
  
  ----
  
negative.code: :imagesdir: images
  :api: http://howardlewisship.com/io.aviso/rook/io.aviso.rook.html#var-rook-dispatcher
  = Rook
  
  Rook is a set of middleware and handlers to enable metadata-based routing for https://github.com/ring-clojure/ring[Ring] web applications.
  