-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Service Arch
-
Fully Compatible
-
Service Arch 2023-10-16, Service Arch 2023-10-30
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
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.