Rethought this a bit.. I previously thought multiple objects on the "network" thread would need to "hold on" to this function, but I think we can just pass it to ClientGetReadReactor which should be able to handle setting the readyState for all stages of the grpc stream request lifecycle.
Details
Details
Will be tested implicitly with subsequent diffs.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- landfeb4 (branched from master)
- Lint
No Lint Coverage - Unit
No Test Coverage