[SERVER-52823] TransportLayer should take a ServiceContext instead of a ServiceEntryPoint Created: 12/Nov/20  Updated: 23/Feb/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: ben-sa-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-52819 Always initialize TransportLayer and ... Closed
related to SERVER-51700 Use TransportLayer to acquire WireSpec Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The ServiceEntryPoint is accessible via the ServiceContext and we can use it to access additional useful decorations. The current form of the TransportLayerASIO constructor is here.



 Comments   
Comment by Blake Oler [ 26/Jan/23 ]

Leaving this closed – we will assess component hierarchy in the networking layer as part of our refactoring projects coming up.

Comment by Lauren Lewis (Inactive) [ 18/Mar/22 ]

We haven’t heard back from you for some time, so we're going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

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