> This is a bit funny in an odd way because I had to disable Nagle to make > performance better with Raw API. For me, performance meant send a command > down with data and get a short response back ASAP.
That's perfectly correct and not odd at all: the nagle algorithm tries to improve the overall network load by not sending too many small packets. What you need is the opposite: low latency. It's perfectly normal on every TCP/IP platform to disable the nagle algorithm for such applications. E.g. remote shells would not work well with nagle turned on as that would introduce a minimum delay of 200ms for every keystroke. Simon -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
