[SERVER-22408] Rehost or replacement of DBClient Created: 01/Feb/16  Updated: 08/Jan/24  Resolved: 01/Oct/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 3.3.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mira Carey Assignee: Backlog - Service Architecture
Resolution: Done Votes: 0
Labels: platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-20667 Only use NetworkInterface (connection... Closed
Duplicate
duplicates SERVER-23448 ASIO based AbstractMessagingPort Closed
Assigned Teams:
Service Arch
Participants:

 Description   

DBClient needs to be rehosted on top of ASIO or replaced entirely with some new abstraction. Probably NIASIO



 Comments   
Comment by Mira Carey [ 01/Oct/19 ]

Around the same time that we introduced network interface tl, we also rehosted dbclient ontop of asio. This work's done

Comment by Mira Carey [ 11/Oct/16 ]

re-opening to remove or replace the implementation (on OP_COMMAND) as part of unified networking in 3.5

Comment by Mira Carey [ 25/May/16 ]

dbclient is backed with an abstract messaging port, so a re-hosting of that type is transitively a re-hosting of dbclient.

We're in the process of putting the abstract messaging port behind an interface on the ingress side, but it'll still be there for egress via dbclient for egress.

We don't currently have anything in the works for replacing dbclient itself.

Comment by Spencer Brody (Inactive) [ 24/May/16 ]

mira.carey@mongodb.com, can you explain how this is a duplicate of SERVER-23488? My impression was that SERVER-23488 is about ingress networking, while DBClient is about egress.

Generated at Thu Feb 08 04:00:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.