anchor.diff:  
   Do not worry about how much data you can send to the client, if you are using
   channels in a right way (in a go block), you will send data to the client as fast
  -as the client can consume it. This technique is also called backpressure, and is
  +as the client can consume it. This technique is also called back pressure, and is
   fully supported for chunked responses.
   
  -Additionaly, you also can return a channel as the handler response. The main
  +Additionally, you also can return a channel as the handler response. The main
   difference is that in this case you should put a complete response into the channel:
   
   [source, clojure]
  
positive.code: (defn login-handler
    [context]
    (let [data (:body context)
          user (find-user (:username data)   ;; (implementation ommited)
                          (:password data))]
      (-> (json/encode {:token (jws/sign {:user (:id user)} secret)})
          (http/ok {:content-type "application/json"}))))
  
negative.code: [[rationale]]
  === What is the rationale behind this project?
  
  I started writing this library as a research project to provide a simple, non
  obstructive (a la ring) without the constraints of the existing ring spec.
  The aim is to create a web toolkit for building asynchronous web services.
  
  