anchor.diff:      (http/ok ch)))
   ----
   
  -Returning a channel as the body has the advantage that you have the ability of setting additional
  -headers and HTTP status in your function body code. But, if you are return a channel as a response
  -value, the default status code will be set for you. The behavior of two approaches is the same,
  -resulting in a chunked encoded response to the client.
  +Returning a channel as the body has the advantage that you have the ability of setting
  +additional headers and HTTP status in your function body code. But, if you are return a
  +channel as a response value, the default status code will be set for you. The behavior of
  +two approaches is the same, resulting in a chunked encoded response to the client.
   
   And this is an example of an async handler returning a channel as response:
   
  
positive.code: 
  ===== Cookies
  
  The cookies CRUD operations works very similiar to the headers one. It consists in two polymorphic
  functions (`get-cookies` and `set-cookies!`) that can be used directly with context or with request
  or response instances.
  
  .Get cookies from request example
  [source, clojure]
  
negative.code: ----
  
  By default, the `application/x-www-form-urlencoded`, `multipart/form-data` and
  `application/json` parsers come out of the box. The
  link:https://github.com/dakrone/cheshire[cheshire] json parser is used for parsing the
  body with the `application/json` content type.
  
  The body parsing is a open system, implemented using clojure's polymorphism facilites
  such as multimethods. If you want add additional parser, is as simple as adding an
  