Connection to Dynamo server

1) Establish connection to Dynamo Server through WebSocket
2) Refactor flood_runner.js to communicate with Dynamo Server
 - For example, "on_addConnection" should be sending message to server
 - Back and forth interactions should show up on Flood console
3) Define JavaScript models for each of the recordable commands
4) Make Flood to use GUIDs instead of int ids
This is the current implementation (before your pull request):

Current implementation - message passing across threads 

FloodRunner  -------  worker.postMessage (e.g. addNode)  ----->  WebWorker (dynamo_runner.js)
FloodRunner <------  postMessage (e.g. onEvalComplete)   ------  WebWorker(dynamo_runner.js)

Your implementation - message passing across processes over WebSocket

DynamoRunner  -------  WebSocket send  (e.g. addNode)              ----->  Dynamo 
DynamoRunner <------  WebSocket send  (e.g. onEvalComplete)   ------  Dynamo

flood_runner.js is the entry point for flood's current engine, which runs in a WebWorker background thread.  The kind of message passing that the Runner and the WebWorker (dynamo_runner.js) do is similar to the kind of message passing that should happen between your implementation of Runner and Dynamo - the only difference being that the latter requires a WebSocket.

That said, your implementation should not require a WebWorker at all, nor should it require modifications to flood_runner.js.  CreateNodeCommand should know the node name from the user's selection.