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
We need a more efficient way to send geometry data (or huge array of primitive types) back to the client. Sending back a text string will definitely not scale. We need to see details of how ```Flood``` makes use of this geometry data, and try to format the result in the way that ```Flood``` expects so it can be used directly without any further conversion (perhaps we should be sending back ```float``` instead of ```double```, depending on how ```Flood``` needs it).

I'd strongly recommend the use of array buffer with some header to indicate the primitive data type. For example, the following format:

```
NodeResult
[ NRES | NodeGuidString | GeometryData ]

GeometryData (for points)
[ PNTS | Count (4 bytes) | VertexData ]
[ PCLR | Count (4 bytes) | ColorData ]

GeometryData (for line strips)
[ LSTP | Count (4 bytes) | VertexData | Strips (4 bytes) | LineStripData ]
[ LCLR | Count (4 bytes) | ColorData ]

GeometryData (for triangles)
[ TRIS | Count (4 bytes) | VertexData ]
[ TRIN | Count (4 bytes) | NormalData ]
[ TVXC | Count (4 bytes) | ColorData ]

[ TriangleVertices | TriangleNormals | TriangleColors ]

VertexData
[ x (4 bytes) | y (4 bytes) | z (4 bytes) ]

NormalData
[ x (4 bytes) | y (4 bytes) | z (4 bytes) ]

ColorData
[ a (4 bytes) | r (4 bytes) | g (4 bytes) | b (4 bytes) ]

LineStripData
[ n (4 bytes) ]
```

Flood client can then receive this as ```Uint8Array``` in binary form through the socket, unpacking the contents to ones that can be used for ```Three.js```. Does that make sense?