Consider reordering arguments to async_rpc::sendCommand functions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • Fully Compatible
    • Service Arch 2023-09-04, Service Arch 2023-09-18
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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. 

            Assignee:
            Erin McNulty
            Reporter:
            George Wangensteen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: