RunwayComponent.cs with HTTPRequest rather than WebClient #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… avoid cache data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I discussed with Vahid a few weeks ago and he encouraged me to contribute. :)
I found that the grasshopper component of Runway always showed the same data values (I tested it with PoseNet using Runway V.0.14.4) when using the network or HTTP. This values would not change over time or when the component was created again so I found that the issue was the cache data. I solved this by using the HTTP request methods rather than the WebClient methods. HTTP allows to define cache policies that avoids storing the data so when the component expires, the information refreshes.
I tested it with some of the existing examples and it works perfectly but it would be ideal if you guys could have a look as you have a holistic understanding of the plugin.
Thank you very much for your time.