anchor.diff:  
   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.
  -
  -Autrement dit, QiWeb n'impose aucun choix technique quand au système de stockage de données utilisé par votre
  -application ni sur la façon dont vous voulez construire vos vues.
  -Il vous laisse le champ libre pour choisir la solution qui vous convient.
   
   image::images/overview.png[Overview,640]
   
  
positive.code: specified using one of the System Properties described above.
  
  
  === Lifecycle and the Global object
  
  ==== Startup explained
  
  
negative.code: 
  === 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.
  
  
  
  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
  
  