anchor.diff:  link:https://facebook.github.io/relay/[Facebook Relay] and
   link:http://netflix.github.io/falcor/[Netflix's Falcor].
   The main differents with them is that this library only represents the transport and
  -message routing layer layer, so it's is nonobstructive and not copupled with
  +message routing layer layer, so it's is nonobstructive and not coupled with
   concrete framework and persistence.
   
   One of the great examples where this library fits in a perfection is a
  
positive.code:               [:any (cauth/auth auth-backend)]              ;; Auth backend
                [:any (parse/body-params)]                  ;; Body parsing
                [:get "login" login-handler]
                [:get some-handler]]))                     ;; (implementation ommited)
  ----
  
  You can see a working example using auth facilities <<website-example,here>>.
  
negative.code: ----
  
  One of the big advantages of using the routing chain for session set up, is that
  you can restrict session handling to a concrete subset of urls/resources avoiding
  unnecessary code execution for handlers that do not need sessions:
  
  [source, clojure]
  ----
  