Reach

1) Implement ComputationResult response with the node data which was changed after execution of RunCancelCommand (values, geometry)
2) Add REST service to retrieve static data (for now it is the list of Node Models)
3) Update models drawing logic to avoid Dynamo crash on subsequent client updates
As a side note, we are doing in/out ports addition in the constructor of the ```NodeModel``` derived classes, and I understand why you'd want to create an instance for each node type. I'm wondering if there's a better way to do it, for example:

1. ```Flood``` queries the full list of library items.
2. ```Dynamo``` sends back the list, without ```Parameters``` and ```ReturnKeys``` information.
3. User searches for an item in ```Flood``` and places it on canvas.
4. Before placement, ```Flood``` sends a query to ```Dynamo Server``` to ask for the number of input/output ports.
5. On request, ```Dynamo Server``` uses ```Activator``` to create a ```NodeModel``` instance, and caches its ```Parameters``` and ```ReturnKeys``` information alongside ```Controller.BuiltInTypeByName``` list.

What do you guys think, @pboyer and @lukechurch? Or is there a better way in the ```Flood``` scenario?