anchor.diff:      (http/ok promise {:content-type "text/plain"})))
   ----
   
  -Thanks to the *future* library internals, we can use it with link:http://fff[cats] `mlet` macro,
  -that allows us structure pure async code in a synchronous way:
  +Thanks to the *future* library internals, we can use it with 
  +link:https://github.com/funcool/cats[cats] `mlet` macro, that allows us structure pure async 
  +code in a synchronous way:
   
   [source, clojure]
   ----
  
positive.code: Here nothing new to explain, if you have a function that return some kind of publisher, you can return
  it as response or send it as body like as usual.
  
  The adaptations and coerciones are done thanks to the link:http://ffff[futura library] that has more
  adaptations supported out of the box that which are comming with _catacumba_.
  
  Let see an example:
  
  
negative.code: === Promises
  
  Promises is an other abstraction supported out of the box in _catacumba_. It comes from the
  link:https://github.com/funcool/futura[futura library] and is build on top of JDK8 _CompletableFuture_.
  
  Sometimes, yo do not need send a chunked stream to the clien, but your "bussines logic" is defined
  with asynchronous friendly api using promises (or something similar). In this case, with _catacumba_
  