Remove lame proof of concept code
Process new websocket requests with individual handlers
Create newGame handler for websocket requests
whitespace
Move ownership and management of renderers out of the game
Let drawSprite look the sprite itself, for future refactoring
Channel game requests into a handler for processing
Merge branch 'tipsy'
Silly golang, your json only works with exported variables
Some Refactoring
Change interface to include the calling client

I'm dissatisfied with this change, but it does function
for now. Something must be done to properly slot in the
clientConnection which made the request into the matching
game, and that requires access to the clientConnection
Slot client connections into their games
Change uncommitedGames to a map for easier everything
Slot in a new handler when a game is committed
Allow messages to be channelled back to the client
Parse and store client info via websocket
Process client disconnections appropriately

The rather complicated slice cutting in removeClientConnection
is there only cause the internet scared me into thinking
removal of an element via append(a[:i], a[i+1:]) might cause
a memory leak. It might not be worth it if it doesn't
Extremely anal whitespace
Change handler channel to buffered

The unbuffered channel blocks for some reason, so this
works for now. The number 5 is pulled from nowhere though
Connect to the server and proxy messages betwixt the client and server