anchor.diff:      
       * _for a non gamer route, `token` could be APISECRET:APIKEY, called **apptoken**_
       * _for a gamer route, `token` is the one returned by sign in/up methods which is an random-key in our cache (redis) pointing a json = { appid: xxx, userid: zzz, ... }, called **gamertoken**_
  +    
  +    _**this means we have 2 redis collections with gamertoken: logged users, revoke at logout, and "active" users in term of CCU, revoked by timeout or suspending app**_
   
   
   ## Gamer Session [/gamer/session]
  
positive.code: ###### response description
  |Field|Description|Value|
  |---|---|---|
  |profile|json| gamer's profile, including "name", "email", "nickname", ...
  |vfs|json| list of key/value associated to the app/game
  |gamervfs|json| list of key/value associated to the gamer
  |matches|json| array of match currently in open state of the gamer
  
  
  + Request (application/json)
  
  
negative.code:         {
              "gamerid" : "identifier of the user" 
              "gamertoken" : "reusable token used by gamer related requests" 
              "profile" : json,
              "vfs" : json,
              "gamervfs" : json,
              "matches" : json array
          }
  
  + Response 401 (application/json)
  