anchor.diff:  (ct/run-server routes)
   ----
   
  -The order of statements is very important because the routing in _catacumba_ is a simple chain or pipeline. 
  +The order of statements is very important because the routing in _catacumba_ is a simple chain or pipeline.
   Each handler has the ability to delegate the request handling to the next handler in the pipeline.
   
   This is a complete list of route directives that you can use a part of `:get`:  `:any` (matches all
  
positive.code: 
  ==== Routing chain
  
  The chaining of handlers can be done in different ways:
  
  - *inline*: providing more that one handler for concrete http method.
  - *multiple route*: providing a "match all" handlers at the start of prefix.
  
  The inline handlers chaining has this aspect:
  
  [source, clojure]
  ----
  (ct/routes [[:get "users" permission-check-handler get-users-handler]])
  ----
  
  Also, you can setup "catch all" handlers at the start and use them as interceptors:
  
  [source, clojure]
  ----
  
negative.code:   (ct/routes [[:get "articles/:id" article-detail]]))
  ----
  
  Additionally to the basic token for representing URL parameters, _catacumba_ also allows the use of
  regular expressions for delimiting the input or marking a URL token optional.
  
  See the following table for all supported URL tokens:
  
  