anchor.diff:  
   === Routes
   
  +Routes are defined by:
  +
  +- a HTTP method ;
  +- a path expression ;
  +- a fully qualified method name ;
  +- optionaly a method parameters definition ;
  +- and finaly optional modifiers.
  +
  +Teh default QiWeb router allows for textual representation of routes definition.
  +
  +    http-method path-expression controller-fqcn.method-name[(parameters)] [modifiers]
  +
  +You can also express routes definitions in code using the Routes API.
  +
   Request URI Path and QueryString are the source of Controller Parameters.
  -Fragment identifier is considered as useful only on the client side and hence is not taken into account when routing.
  +
  +
  +
  +TIP: URI Fragment identifier is considered as useful only on the client side and hence is not taken into account when routing.
   However, the reverse routing API allow you to append a fragment identifier to generated URIs.
  +
   
   === Controllers
   
  
positive.code: 
  The QiWeb Runtime use http://slf4j.org/[SLF4J] and http://logback.qos.ch/[Logback] logging and do not do anything
  special regarding its configuration.
  This means that you have full controll of Logback configuration.
  Therefore you are encouraged to read the official http://logback.qos.ch/documentation.html[Logback documentation].
  
  All QiWeb loggers are present in the `org.qiweb` namespace.
  Here are the most useful:
  
  - `org.qiweb.runtime.server` QiWeb Http Server
  
negative.code: 
  In other words, QiWeb don't compell you to use any persistence mechanism nor templating engine.
  You are free to choose whatever may suit your needs.
  
  image::images/overview.png[Overview,640]
  
  