anchor.diff:  * Convenience helpers for common handlers operation.
   
   In a catacumba design (inherited from ratpack), a handler is a unit of work in
  -an asynchronous handler and the context is a execution controler and local storage
  -for the current request state.
  +an asynchronous handler pipeline and the context is a execution controler and
  +local storage for the current request state.
   
   In other words it can be explained as "flow control" in the chain of handlers.
   
   The request process is an asynchronous pipeline of handlers that can be
  -composed in different ways (as we previously seen in a router section). So the each
  -handler in the pipeline has the ability to do some work and delegate the rest of
  -processing to next handler in the chain.
  +composed in different ways (as we previously seen in other parts of the
  +documentation). So the each handler in the pipeline has the ability to do some
  +work and delegate the rest of processing to next handler in the chain.
   
   This approach allows you build different kind of modular and completelly decoupled
   handlers and compose them into a pipeline to work together.
  
positive.code: === What is the difference between _catacumba_ and Aleph?
  
  First of all, Aleph is not a real alternative to catacumba, because its approach is
  so much low level and its web server support is a little bit constrained by ring.
  Furthermore, aleph is already used in catacumba as http client in tests code and
  manifold (async abstractions behind aleph) as one of the first class abstractions
  for handle async vales.
  
  So, I'm happy to tell you that you can use the both libraries together because
  they are very complementary.
  
  
  == Developers Guide
  
negative.code: _Catacumba_ is an asynchronous or non-blocking web toolkit for Clojure built on top
  of ratpack and netty drawing inspiration from ring, pedestal and ratpack.
  
  [NOTE]
  ====
  *Project Maturity*: +
  Since _catacumba_ is a young project there may be some API breakage. +
  
  *Rationale*: +
  You can read the rationale behind this project <<rationale,here>>.
  ====
  
  
  [[quickstart]]
  == Quick Start
  
  This section intends to explain how to get _catacumba_ up and running.
  
  
  === Install
  