A single socket with a reader thread and a writer thread

Question

Could a socket handle reading and writing simultaneously? If it could, are there any impact?
Thanks

Answer 1

With a single socket, a client sent , for example, the first 10 IP packages and wait for the server acknowledge.TCP does that asynchronously from the application.
If the server noticed that the 7th package was corrupted, then the client need to resend the 7th package.TCP does that asynchronously from the application.
This could imply there were some idle times on both the client and server.Not at the client. TCP does all that asynchronously from the application. Data is written from the application into the socket send buffer and then the client continues execution. All the segmentation and packetization and acknowledgement and retry is asynchronous from the application. There is a delay at the server but's that's because all the data hasn't arrived, innit? so it's unavoidable. But in practice very few packets are lost and TCP runs at pretty much full speed all the time.
You still haven't clarified whether you're talking about your code or TCP, but if you're not talking about what TCP does, you must be trying to build all this stuff into your application, which I've already spoken about as redundant at best and highly counter-productive at worst.
If I open multiple sockets between the client and the server, these idle times would be minimize since the client , while waiting for the acknowledge, could send data to other sockets.This is fallacious for the reasons given above.