anchor.diff:  
   === Contributing
   
  -**catacumba** unlike Clojure and other Clojure contrib libs, does not have many
  -restrictions for contributions. Just open a issue or pull request.
  +Unlike Clojure and other Clojure contributed libraries _catacumba_ does not have many
  +restrictions for contributions. Just open an issue or pull request.
   
   
   === Source Code
  
positive.code: 
  ==== Strict Transport Security
  
  This is a security related chain handler that adds the `Strict-Transport-Security` to the response.
  
  HTTP Strict Transport Security (often abbreviated as HSTS) is a security feature that lets a web
  site tell browsers that it should only be communicated with using HTTPS, instead of using HTTP.
  
negative.code: == FAQ
  
  [[difference-with-aleph]]
  === What is the difference between _catacumba_ and Aleph?
  
  First of all, Aleph is one of the most robust libraries in the Clojure ecosystem for building asynchronous
  servers. Here is an incomplete list of differences and motivations why I wrote _catacumba_ instead
  of using _aleph_ directly in my applications:
  
  - Aleph with manifold offers good abstractions for creating async servers but they are much too
    low level and only provide the basic building blocks. _catacumba_ intends to be a toolkit that is highly
    focused on web development by providing a good collection of features that matter to web developers.
  - I wrote _catacumba_ to have an alternative to ring and _Aleph_ that uses ring's abstractions for
    handling web requests.
  - Aleph has a good path to have an easily readable  and user friendly documentation.
  - Aleph is build on manifold streams and _catacumba_ uses reactive-streams abstractions.
  
  