writev behavior for bound message-oriented sockets
The writev function that I see in this source code simply iterates over the vectors calling write() for each.
This should work reasonably well for stream-oriented sockets where writes are just combined into the byte stream.
For message-oriented sockets (like UDP) the behavior will be different than writev would typically give. The way I read this code, I believe it would create one packet per iov buffer (assuming a UDP socket in the connected/bound state).
@txtdawg I saw this issue, it will take approximately 24 hours to resolve it. Waiting for assignation of PR.
FYI, @CoderRC
I accepted a new commit to create one packet per iov buffer. All should be done is repeat the process again. Reply if it is fixed or not.
You should close this issue