Existing PrimaryOnlyService implementations have created some existing calling-conventoins for async APIs that take in executors as work-contexts and CancellationTokens for cancellation. Additionally, the server has some best practices around ordering different types of arguments (pointer vs reference vs optional). We should change the argument ordering for sendCommand to match these conventions and expectations.
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: