-
Read your socket buffers quickly
-
With a single connection, there is less buffering
-
If you don't read the data, you'll slow TCP down (delayed ack's)
-
We had to insert a thread in the library to agressively get data out
of the operating system
-
Would like better control and information than the socket interface
currently provides:
-
Control of TCP window independent of socket buffer
-
Would like MSS size of network
-
Would like network RTT timer from TCP
-
Would like bandwidth statistics from TCP
-
Tools are your friends. Without them, it will take you much longer
to figure out why your code is running slowly (or that your TCP stack is
buggy)
-
Beware of buggy TCP implementations
-
Unfortunately, you can't presume your TCP implementation works correctly
-
While your library can/should automatically send a request buffer automatically,
your application has even better knowledge of when to flush the output
buffer
-
Set TCP_NODELAY to disable Nagle's algorithm