anchor.diff:  ---------------------------------------------------
   package conf;
   
  +import com.google.inject.Singleton;
  +
   import io.mangoo.interfaces.MangooLifecycle;
  -
  -import com.google.inject.Singleton;
   
   @Singleton
   public class Lifecycle implements MangooLifecycle {
   
       @Override
  +    public void applicationInitialized() {
  +        // Do nothing for now
  +    }
  +
  +    @Override
       public void applicationStarted() {
  -        //Do nothing for now
  +        // Do nothing for now
       }
   }
   ---------------------------------------------------
   
  -Please note, that the Lifecycle class doesn't have to be named
  -"Lifecycle", but must implement the MangooLifecycle interface and that
  +[NOTE]
  +The Lifecycle class doesn't have to be named
  +"Lifecycle", but the class must implement the MangooLifecycle interface and that
   you have to bind the implementation using Google Guice in your Module
   class. The module class is also located in the /conf package in your
   application. This class can also hold other custom Google Guice bindings.
  
positive.code: === Session encryption
  
  By default the values in the client-side cookie are signed with the
  application secret using SHA2(SHA-384), making manipulation of the
  values very hard. The security of the client-side cookie can be further
  increased by using AES encryption. To activate cookie encryption of the
  session cookie, set the following propertiy in your application.yaml
  
  ----------------------
  cookie:
  
negative.code: 
  If you don't have a pojo you want to map the request JSON content,
  mangoo I/O offers you a generic way of retrieving the content through
  the object body of a request to a Map<String, Object>.
  
  [source]
  --------------------------------------------
  