[SERVER-81549] Make ServiceContext::getTransportLayer return a TransportLayerManager Created: 28/Sep/23  Updated: 29/Oct/23  Resolved: 20/Oct/23

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

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

Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-10-16, Service Arch 2023-10-30
Participants:

 Description   

Now that there can be multiple transport layers configured for one service context with gRPC, we should make ServiceContext::getTransportLayer return a TransportLayerManager, so that we can separately deal with the configured egressLayer and the different ingressLayers when we get the TL from the service context.

We will also want to add on a `getEgressLayer()` function to TransportLayerManager so that we can access the specific egress layer, and downcast it to a gRPC or Asio TL.



 Comments   
Comment by Githook User [ 20/Oct/23 ]

Author:

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

Message: SERVER-81549: Make ServiceContext::getTransportLayer return a TransportLayerManager
Branch: master
https://github.com/mongodb/mongo/commit/1fa5681e02e4bc68f148a2d64234753dad0bd4ee

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