>TCP_NODELAY is not a POSIX feature, and the common UNIX/Linux behavior >is to allow it to be set/unset at any time. Strange the Windows would >be restrictive in this way.
We were easily able to reproduce errors on Windows trying to set this option after the connection was established, but it didn't occur every time. The documentation didn't list any specific restrictions, but our guess is that Windows requires that it be set before any data is sent or received on the socket. In any case, the errors went away after moving the call before connect. - Sean _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
