anchor.diff:  
   It is your responsibility to store these to help the user log in later.
   
  -Login for authenticated gamers will one of these : 
  -
  -* Facebook identity: use the `ID` and the `oauth token` from Facebook
  -
  -* Google+ identity: use the `ID` and the `oauth token` from Google+
  -
  -* RAW: use the `gamer_id` and the `gamer_secret` from a previous login
  -
  -    Note: I've added RAW as a mean to login again, with gamer_id:secret
   
   ###### body description
  +
  +A JSON object must be sent in the request body with the following structure.
   
   |Field|Description|Value|
   |---|---|---|
   |network|string, required|can be one of ["raw", "facebook", "googleplus"]
  -|facebookid|string, required when {network=facebook}| the ID returned by facebook sdk
  -|facebooktoken|string, required when {network=facebook}| the token returned by facebook sdk
  -|googleplusid|string, required when {network=googleplus}| the ID returned by google sdk
  -|googleplustoken|string, required when {network=googleplus}| the token returned by google sdk
  -
  -    Note: maybe we should use `network, id, token` instead, to remove any ambiguity that login is using a single network...
  +|id|string, required | the user ID for this network
  +|token|string, required| the user secret/token for this network
   
   ###### response description
  +
  +The response is a JSON object.
  +
   |Field|Description|Value|
   |---|---|---|
   |gamer_id|string| user_id used in basic authentication for gamer authenticated requests
  
positive.code: 
  + Response 200 
  
  
  ## Gamer VFS  [/gamer/vfs/{domain}/{key}]
  
  ### Get gamer's data [GET]
  
  ###### Possible values for error 404
  * `Key not found` ... the specified key doesn't exist
  * `Domain not found` ... the specified domain doesn't exist
  
      Note: it should be 404 (resource not found), not 400 (bad request)
  
  ###### response description
  |Field|Description|Value|
  
negative.code: 
  ## Login [/v1/gamer/login]
  
  
  The login route is used to authenticate a gamer, and get basic profile information about him.
  
  Login for authenticated gamers will one of these : 
  
  * Facebook identity: use the `ID` and the `oauth token` from Facebook
  
  * Google+ identity: use the `ID` and the `oauth token` from Google+
  
  * RAW: use the `gamer_id` and the `gamer_secret` from a previous login
  
      Note: I've added RAW as a mean to login again, with gamer_id:secret
  
  After login has been called, HTTP Basic Authentication will be used to authenticate every requests.
  
  |Header     |               |
  |---        |---            |
  