[SERVER-51700] Use TransportLayer to acquire WireSpec Created: 16/Oct/20  Updated: 29/Oct/23  Resolved: 11/Sep/23

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Erin McNulty
Resolution: Fixed Votes: 0
Labels: neweng, servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49157 Initialize WireSpec during MONGO_INIT... Closed
is depended on by SERVER-80820 Create getters for Specification on o... Backlog
is depended on by SERVER-80822 Move WireSpec Parameters out of code ... Backlog
is depended on by SERVER-80823 Remove gRPC uses of getGlobalServiceC... Backlog
Related
is related to SERVER-52823 TransportLayer should take a ServiceC... Open
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-09-04, Service Arch 2023-09-18
Participants:
Story Points: 3

 Description   

We still have a number of calls to WireSpec::instance() which uses a global variable. We should switch to using the TransportLayer::getWireSpec() via the ServiceContext. Often, we can go from Session to TransportLayer. Otherwise, this may still rely on getGlobalServiceContext(), but we already know we want to change those locations when possible.

Acceptance criteria: 

We should switch to using the TransportLayer::getWireSpec() via the ServiceContext.
Remove WireSpec::instance()



 Comments   
Comment by Githook User [ 11/Sep/23 ]

Author:

{'name': 'Erin McNulty', 'email': 'erin.mcnulty@mongodb.com', 'username': 'erin2722'}

Message: SERVER-51700: Made WireSpec decorator of ServiceContext instead of Singleton
Branch: master
https://github.com/mongodb/mongo/commit/adaec3102fe3a63f46c36d78cbf39cfde3e91f8b

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