anchor.diff:    (http/internal-server-error (.getMessage error)))
   ----
   
  +
   ==== Serving static files
   
   _Catacumba_ also comes with the ability to serve static files. This is can be done using
  
positive.code: (defn my-async-handler
    [context]
    (let [pub (->> (stream/publisher ["hello" " " "world"])
                   (stream/publisher (map str/upper)))]
      (http/ok pub)))
  
  ;; It will return a chunked response to the client with "HELLO WORLD" string.
  ----
  
  
  === Websockets
  
  One of the main goals of _catacumba_ is come with builtin, full featured and
  backpressure-aware websockets support.
  
negative.code: the internal terminology).
  
  
  === Context
  
  The second thing most important in the catacumba terminology is a *context*. It can be
  considered a central part of both: IO and the execution flow control (will be explained
  in advanced section).
  
  
  ==== Send a response
  
  As you can observe 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:
  
  [source, clojure]
  ----
  