Wednesday Scrum and Pair Programming

The biggest changes we decided to make today are a switch from UDP for game joining to TCP. This will make the server joining code more robust. However, it is more difficult to code. Instead of broadcasting UDP packets willy-nilly, we need to coordinate between the host and client some handshaking.

However, this will help in the long run as the games themselves will rely on TCP connections for communication. We are using the same TCP approach that our previous project, IRLHvZ, used.






Currently, we can host a game with and without passwords. This opens a lobby for the host that lists the players in the game. Clients can refresh the list of current open game lobbies. They can see if they are password protected or not. They can select which lobby to enter and are prompted to enter a user name (and password when applicable). When a player enters a lobby, the host of the lobby is notified and the player list is updated. The player is presented a lobby screen showing the current players in the lobby and the general game information. The clients can also choose to leave the lobby. This brings the client back to the main menu. It also updates the host about the client leaving, updating the list of players. The other players in the lobby are also notified of this change.

What we need to do in the next sprint is implement an actual game.

We did not complete as much as we wanted to this sprint. This was due partially to traveling by both Derek and myself. However, a good portion of this setback was that I was bedridden for all of last week. Since this sprint was primarily pair programming, little work was done while I was sick.

Today's work was done from 7:00pm to 9:00pm in Derek's room. He was driving and I was navigating. Again, this works because he knows the ins and outs of Android programming and I am more familiar with network programming. I can tell him what to type, and he knows where to type it. As a result, I am getting better at android programming and Derek is getting better at network programming.