anchor.diff:  
   The login route is used for authenticate a gamer
   
  -HTTP Basic Authentication is used to authenticate all other requests, using the token returned by the request.
  -
  -The response contains  a `gamer_token`. Its an opaque value and will be used to authenticate the gamer (with HTTP Basic Authentication).
  -
  -It is your responsibility to store the gamer_token to help the user log in later.
  -
  -Login for authenticated gamers will one of theese components: 
  +HTTP Basic Authentication is used to authenticate every requests, using the token returned by the request.
  +
  +|Header     |               |
  +|---        |---            |
  +|x-apikey   |Your API key   |
  +|x-apisecret|Your API secret|
  +|BasicAuthentication| gamer_id:gamer_secret base64 encoded|
  +
  +Both `gamer_id` and `gamer_secret` are returned by `/v1/gamer/login`.
  +
  +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
   
   |Field|Description|Value|
   |---|---|---|
  -|network|string, required|can be one of ["email", "facebook", "googleplus"]
  +|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...
  +
   ###### response description
   |Field|Description|Value|
   |---|---|---|
  -|gamertoken|string| token used in basic authentication for gamer authenticate requests
  +|gamer_id|string| user_id used in basic authentication for gamer authenticated requests
  +|gamer_secret|string| secret used in basic authentication for gamer authenticated requests
   |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
  
positive.code:     
              x-apikey : test_api_key
              x-apisecret : test_api_secret
              Authentication : Basic gamertoken
              
  + Response 200 (application/json)
  
  
negative.code: 
  ## Authentication
  
  Once you've created an account, you can provision a Game in the FrontOffice application in either sandbox or production mode.
  We're using a classic APIKEY / APISECRET couple to authenticate all requests.
  
  Every request should have two headers set with your game credentials :
  