unit tests passing, we are currently using this
functionality in our environment with a custom consensus stack. In our world,
we have a C++ plugin that calls out to an HTTP REST service (implemented in
Java/Scala, not that it matters).
Thanks,
Mark Cavage
n try to load a plugin. This should be the least
disruptive behavior (imo), and module authors don't need to worry about
anything else "legacy."
- Mark
---
This is an automatically generated e-mail. To reply, visit:
https://re
/diff/
Testing
---
In addition to all unit tests passing, we are currently using this
functionality in our environment with a custom consensus stack. In our world,
we have a C++ plugin that calls out to an HTTP REST service (implemented in
Java/Scala, not that it matters).
Thanks,
this
functionality in our environment with a custom consensus stack. In our world,
we have a C++ plugin that calls out to an HTTP REST service (implemented in
Java/Scala, not that it matters).
Thanks,
Mark Cavage
there's precedence. Changed back to using `Option`.
- Mark
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43269/#review119232
-------
using this
functionality in our environment with a custom consensus stack. In our world,
we have a C++ plugin that calls out to an HTTP REST service (implemented in
Java/Scala, not that it matters).
Thanks,
Mark Cavage
world,
we have a C++ plugin that calls out to an HTTP REST service (implemented in
Java/Scala, not that it matters).
Thanks,
Mark Cavage
