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: 
  [source,java]
  ----
  public Outcome aControllerMethod()
  {
      String configValue = application().config().getString( "your.custom.config.key" );
      // ...
      return outcomes().ok().build();
  }
  ----
  
  All configuration properties can be overriden by defining System Properties.
  This means that you can easily provide all configuration on the command line.
  
  Moreover, some special System Properties allow to use an alternate config file:
  
  
negative.code: === Configuration
  
  INFO: QiWeb configuration use the https://github.com/typesafehub/config/blob/master/HOCON.md[HOCON format] ("Human
  Optimized Config Object Notation"). It is parsed using https://github.com/typesafehub/config[Typesafe Config].
  
  The `application.conf` file must be present at the root of your classpath and must at least contain one single entry:
  `app.secret` which is the secret key your application will use to sign session cookies.
  