Soooo, since they know the length it means they know the data to send,
which means there is no valid excuse for not sending all the data at one
time - ie in one call to the transport. Their use of TCP_NODELAY was
simply a kludge, and a massive one at that.
I still think there are issues trying to map the byte-based RFC cwnds to
a packet based cwnd in the stack, but the application is defintely broken.
Even doing it two pieces (header and data) would have worked.
Insofar as it would not have stumbled over the cwnd.
Still it should be presenting everything at one time - is there no
gathering send to be made?
rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
