anchor.diff:  
   As QiWeb is stateless oriented, it provides no way to keep session state server side.
   Instead a simple session Cookie is used to keep state accross user requests.
  +
  +TIP: If you need to keep server side state think about your database or cache system of choice.
   
   The Session Cookie contains a `Map<String,String>` and is signed using the mandatory Application Secret.
   Signature use the HmacSHA1 algorithm.
  
positive.code: 
  Request URI Path and QueryString are the source of Controller Parameters.
  
  
  NOTE: 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.
  
  
  
negative.code: - optionaly a method parameters definition ;
  - and finaly optional modifiers.
  
  The default QiWeb router allows for textual representation of routes definition.
  
      http-method path-expression controller-fqcn.method-name[(parameters)] [modifiers]
  
  