Now when packaging a Board, I save the names of the object class names and reconstruct the objects as the extended classes rather than the generic parent classes. Note this requires each child class to have its own explicitly scpecified default constructor. Client can now submit whose turn it is to the server.
Started implementing users table.  Server saves whose turn it is as specified by the client.
Refactored my http connection code.  I realized all request methods are the same, after being executed by the httprequest, their responses need to be parsed.  Therefore I have a generic async task that sends an array of requests and another that handles all the parsing.  I added in a few tests for retrieving Users from the Users table including new User->JSON interface.
Added Users Table and servlet.  Remember that all responses from the servlet return an array of objects.
Added all tests for UsersTable to TestBench.  Changed packages around.  Added an abstract ResponseParserJSON class that can be extended to return a list of your objects as long as the input stream from the server contains a JSONArray of your objects.
Added Teams table to server along with an untested API.  I realized a lot of code is duplicated between tables.  I am currently looking for a way to abstract out the common traits between tables.  For example, ever time we get an object out of a table, we call a method to turn the column values into a JSON object.  The only code that changes are key value pairs and I copy and paste a lot of other code to piece the JSONObject into an array.  Also, the UtilsJSON seems to be specific to each table, pretty inconvenient utility.
added specific teams to play on two different devices