Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-68650

Cleanup remote_command_runner naming conventions

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-10-17, Service Arch 2022-10-31

    Description

      For the classes I implemented in the executor/ folder, I qualified them with the namespaces `executor` and `remote_command_runner`. However, for the classes I implemented outside of the `executor/` folder, I just qualified them with the `remote_command_runner` namespace. This is confusing the compiler, and so we need to brainstorm and implement a general solution to the namespaces for this API.

       

      Broadening the scope of this ticket a bit - we'll now 

      -> replace all uses of executor::remote_command_runner and remote_command_runner with the single async_rpc namespace

      -> Change the naming of the public API and all public types to match

      Attachments

        Activity

          People

            george.wangensteen@mongodb.com George Wangensteen
            erin.mcnulty@mongodb.com Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: