Caching & repeated execution #21
Description
From @radumg on December 24, 2017 17:23
Expected Behavior
Executing a graph with DynaWeb nodes a second (or Nth) time should consistently produce the same result.
Actual Behavior
Repeated execution of the same graph can have unintended consequences :
- may send malformed requests (doubled up headers for example)
- fail to send an identical request a second time.
Main reason for this is Dynamo's caching of node results.
Note that I've successfully tested a workaround : using the ProRUBIM node that forces execution of children nodes. This suggests that these shortcomings can be tackled by using NodeModels so a discussion around this is needed.
Copied from original issue: radumg/DynWWW#41