Save and Load Server Communication

Purpose

This Wiki page is to provide documentation for the latest implementation of the GAMESTATE Database Table as well as the Responses the Server will accept to the database and the format Queries from the client side should take. This is closely related to the work taking place on ticket #10.

GAMESTATE Table Structure

Row Name	Type	Restrictions	Description
STATEID	varchar(64)	Primary Key	Used to uniquely identify each GameState in conjunction with USERID
USERID	varchar(64)	NOT NULL, Foreign Key	FK (USERID) Reference USERS(USERID)
GAMEDATA	clob	NOT NULL	The actual save Data JSON string is stored here
TIMESTAMP	timestamp	NOT NULL	Stores the time at which the GameState was saved

The foreign key from the Users table is created when a user creates an account

Client Side Queries

A valid client side query must include a:

• GameState Data Access Object (StateDao)
• User Data Access Object (userDao)
• Token Data Access Object (tokenDao)

Maintainers

This Wiki is being maintained by Team Leave Britney Alone, if you feel anything needs further clarification or needs to be added please ping @lyndonmoore on slack.