CP-51693: introduce feature flag to use JSONRPC for internal pool communication #6123
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.
XenCenter uses JSONRPC, and our SDK also prefers it.
Benchmarks have also shown that the OCaml implementation of xmlrpc is slower than jsonrpc.
In order of decreasing speed: CSexp > JsonRPC > Sexplib > XmlRPC
This PR just introduces a feature flag, but doesn't enable it yet (it can be enabled in xapi.conf, or by inheriting from this branch and flipping the boolean, which is what I've done to test it)