anchor.diff:  
   === Running the server
   
  -Now having defined the simple, hello world handler, it is time to run it. To do it,
  -import the `run-server` function from `catacumba.core` ns and execute it with
  -handler as first parameter:
  +Having defined the simple, hello world handler, it's time to run it. To do this,
  +import the `run-server` function from the `catacumba.core` ns and execute it with
  +the handler as the first parameter:
   
   [source, clojure]
   ----
  
positive.code: [org.slf4j/slf4j-simple "1.7.12"] ;; (optional, only for show ratpack info messages)
  ----
  
  _Catacumba_ is only runs with *JDK8* and *Clojure 1.7+* (due to extensive use of
  transducers and jdk8 concurrency primitives).
  
  
  
negative.code: 
  
  NOTE: I mention the "default" word because, _catacumba_ comes with different
  <<handler-types,types of handlers>> out of the box. Catacumba's handler system
  is fully extensible so you can easyly create your own handler types (also called
  adapters the internal terminology).
  
  
  === Context
  
  The second thing most important in the catacumba terminology is the *context*. It can
  be considered a central part of both: IO and the control flow (will be
  explained in advanced section).
  
  
  ==== Send a response
  
  As you can see from the previous example, no status code is being provided,
  only the body of the response. To send a complete response you can use a builtin
  response type:
  
  