Why is my tcp not reliable? (2009)

Re:Why is my tcp not reliable? (2009) by benchaney on Saturday April 01, 2017 @08:34PM (#14015005)

I've always thought that this is ridiculous. Once a TCP socket reports that data has been sent, it should continue working to send it until every bytes has been acked (with the exception of an unrecoverable failure case). Also, I wish there were an API to detect how much data still hasn't been acked.

[ Parent | on HN ]

Re:Why is my tcp not reliable? (2009) by gmazza on Saturday April 01, 2017 @09:08PM (#14015119)

> I wish there were an API to detect how much data still hasn't been acked.

From example code attached to the original article (Linux only):

  int outstanding;
  ioctl(fd, SIOCOUTQ, &outstanding);

[ Parent | on HN ]

Re:Why is my tcp not reliable? (2009) by wyldfire on Sunday April 02, 2017 @11:40AM (#14017529)

You have to be pretty careful about what conclusions you draw from this info. It means relatively little about what your actual peer has seen. It tells you a some info about the channel between you and your peer, though.

If you need detailed feedback, you need to implement a feature that closes the loop.

[ Parent | on HN ]

Re:Why is my tcp not reliable? (2009) by astrobe_ on Sunday April 02, 2017 @09:58AM (#14017181)

I guess that select() already had a meaning so it couldn't be used for this?

[ Parent | on HN ]