anchor.diff:  - resolve application routes
   - activate registered plugins
   - resolve plugins routes
  -- notify global of application activation
  +- notify the Global object of application activation
   - bind HTTP server
   
   After that, the application is ready to process requests.
  
positive.code: responses.
  
  If your application is running on multiple nodes behind a balancer you can lower this value to 0, yes *zero*, allowing
  your clients to reconnect immediatly to another node. Pretty useful for zero-downtime upgrades.
  
negative.code: 
  While startup fail fast, shutdown fail safe.
  In other words, startup fail on first error while shutdown always succeed.
  If errors happen during shutdown they are collected and logged once shut down in a single stacktrace thanks to Java 7
  suppressed exceptions.
  
  Application shutdown is sequential and pretty straightfoward:
  
  - unbind HTTP server
  - notify the Global object of application passivation
  - passivate registered plugins
  - stop application thread pools
  
  ==== Graceful shutdown
  
  