From: Phillip Susi
The delayed ACK is also correct behavior. Since there is plenty of room left in the window, the ACK is supposed to be delayed so it can ACK further data with one packet.
I'm not arguing that delayed ACK is incorrect, but 2.5 sec??? Searching the Internet, 200ms seems a much more accepted value. This is also the value used by the MS stack: http://www.microsoft.com/technet/itsolutions/network/deploy/depovg/tcpip2k.m spx (under "Delayed Acknowledgements").
My current conclusion is that mozilla is poorly behaved because it sends one byte at a time. Heck, it shouldn't even be using tcp/ip for local IPC.
You might want to cut them some slack, their code needs to be cross-platform. TCP/IP is available on every platform they support, otherwise a browser doesn't make much sense :-)
You might want to file a bug with them on this issue.
No, it is our job to make ReactOS behave like Windows, not the job of the app vendors to change their code to suite ReactOS.
If they do set that flag and ReactOS does not correctly implement it, that would explain why it works ok on windows and not ReactOS.
My test program does not set that flag and still works ok on Windows.
Thanks for your input, I really appreciate it (and learn a lot of new things).
GvG