[CXX-114] Allow clients to provide their own implementations of the socket API Created: 08/Dec/11  Updated: 07/Jan/15  Resolved: 07/Jan/15

Status: Closed
Project: C++ Driver
Component/s: Implementation
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: cxxmove, legacy-cxx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends

 Description   

If users of the C++ driver could provide their own socket API calls, they could do things like provide asynchronous versions of the calls.

One idea is to change sock.cpp to instead of calling the native socket syscalls (send, recv, connect, etc.) to wrap them in other functions that are implemented in a separate file so that it when the driver is compiled a user could link in a different file with different socket functions.

Another idea is to allow the user of the API to initialize it with a set of function pointers for the system calls that defaulted to passthroughs.


Generated at Wed Feb 07 21:58:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.