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.