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
That's a valid argument, @marimano. It is hard to tell how slow or fast things will really be, and in my scenario, network latency could bring the whole experience down. This part is actually rather "okay" to me so we can leave it as that, in the future our server can be made to collect usage information and rank nodes based on their frequency of use. Perhaps top used nodes will be sent once to the user, whereas the rest can be retrieved on-demand. I think we can leave this as it is for now, thanks.