Build API layer for communication to games

[eonarheim]

We need to build the api layer

• [x] Implement the api logon per specification (look at ants game for examples)
• [x] Implement specific command end points
• [x] Validate commands are correct when the hit the endpoint
• [x] Write tests if able (mock game engine context)

[FourierTransformer]

GET: "api/game/logon" Returns:

{
    "AuthToken": "crazy-token-goes-here",
    "GameID": 51
}

POST: "api/game/{id}/update/{AuthToken}"

{
    "MoveRequest": [
        {
            "ElevatorID": 5,
            "Function": "MoveUp"
        },
        {
            "ElevatorID": 7,
            "Function": "MoveDown"
        },
        {
            "ElevatorID": 9,
            "Function": "TransferPeople"
        }
    ]
}

Returns:

{
    "RequestStatus": [
        {
            "ElevatorID": 5,
            "Success": true
        },
        {
            "ElevatorID": 7,
            "Success": true
        },
        {
            "ElevatorID": 9,
            "Success": true
        }
    ]
}

GET: "api/game/{id}/status/{authToken}" Returns: https://gist.github.com/FourierTransformer/fe898d727b0a95437a1a (a little long to post here) UPDATE: the gist now shows the number of people waiting to go up/down because more info is more info!

Will each person have their own "frustration" time (like 2*[the number of floors they wanted to travel]) or will it be some static variable? (it slightly changes how/what this returns)

[FourierTransformer]

looks like #6 helps address some of the concerns. I'll update the sample JSON to show the changes!