[SERVER-68650] Cleanup remote_command_runner naming conventions Created: 08/Aug/22  Updated: 29/Oct/23  Resolved: 19/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Erin McNulty Assignee: George Wangensteen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-10-17, Service Arch 2022-10-31
Participants:

 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



 Comments   
Comment by Githook User [ 19/Oct/22 ]

Author:

{'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}

Message: SERVER-68650 Improve async RPC API naming conventions and fix use of retry policy
Branch: master
https://github.com/mongodb/mongo/commit/f84dd22211da9ed5865e5ea11f7a189e95e07f20

Generated at Thu Feb 08 06:11:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.