Is TCP_NODELAY actually the right way to disable Nagle on Windows? The Microsoft documentation at http://msdn.microsoft.com/en-us/library/windows/desktop/ms740476(v=vs.85).aspx says that "This socket option is included for backward compatibility with Windows Sockets 1.1" which implies that there's some better way to do it.
On Fri, Jun 13, 2014 at 08:45:32PM +0000, Linda Sun wrote: > On windows platform, setsockopt would return invalid argument if > called before tcp is connected. > > Linda > > -----Original Message----- > From: Ben Pfaff [mailto:b...@nicira.com] > Sent: Friday, June 13, 2014 1:36 PM > To: Linda Sun > Cc: dev@openvswitch.org > Subject: Re: [ovs-dev] [PATCH] Only set TCP_NODELAY after connection is > established for SSL. > > On Fri, Jun 13, 2014 at 01:35:18PM -0700, Linda Sun wrote: > > Signed-off-by: Linda Sun <l...@vmware.com> > > Why? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
