anchor.diff:  
   ### Set gamer's data [PUT]
   
  +You can store data easily. Simply send the data to be stored, as a JSON object, in the body of the request. Note that simple strings are not allowed. Arrays and objects are.
  +
   **if domain and/or key don't exist, they are created**
   
   + Parameters
  
positive.code: Your game has its own private Domain (see in FrontOffice dashboard) which you probably don't want to share
  but you can create other domains to share data between apps, or even between app-developers.
  
      I think we could use a magic `private` domain, replaced on the server with the apisecret (or a derived id).
      It will provide secure game-private data.
      Similarly, we could offer a magic `public`domain, not replaced on the server... but I'm against it, as it
      gives the impression we don't take security seriously enough
  
      Anyway, I think we'll need, in the Game collection: the domains created by the dev, and the domains 'imported' by the dev
      This will provide an additional level of security, and we'll have a list of valid domains to add stuff later
  
  
negative.code:     
  ### Remove gamer's data [DELETE]
  
      NOTE : we can't yet distinguish a missing key from an incorrect domain...
  
  ###### Possible reasons for error 404
  * `Key not found` ... the specified key doesn't exist
  * `Domain not found` ... the specified domain doesn't exist
  
  + Parameters
      + domain (required, string) ... the domain from where to get the key/value
      + key (optional, string) ... the key to be removed (all if not specified)
  
  + Request
  
  