What you see is the Naggle algorithm. It is the old trade off, delay or throughput. If your application requires throughput, you want it. If you do need short delay, it can usually be minimized by some configuration function/option. The RAW API lets you tweak mostly at will, but the interface is not as friendly as sockets and definitely not standard. In all cases, the amount of bytes delivered at the other end is not necessarily related to your calls to the API; though it can be tamed by proper config and/or calling. There are many threads in the list on this very subject, you can search for some or wait for one of the gurus to give you some clues. For the socket stuff, it is mostly standard.
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
