From: Jan Matejka <Jan.Matejka@...>
Date: 2001-09-26T18:37:21+09:00
Subject: [ruby-talk:21715] Re: Repost. Final call for help on this piece of code...

Excerpt from setsockopt documentation (Platform SDK: Windows Sockets
Documentation):

TCP_NODELAY

The TCP_NODELAY option is specific to TCP/IP service providers. The Nagle
algorithm is disabled
if the TCP_NODELAY option is enabled (and vice versa). The process involves
buffering send data
when there is unacknowledged data already in flight or buffering send data
until a full-size packet
can be sent. It is highly recommended that TCP/IP service providers enable
the Nagle Algorithm
by default, and for the vast majority of application protocols the Nagle
Algorithm can deliver significant
performance enhancements. However, for some applications this algorithm can
impede performance,
and TCP_NODELAY can be used to turn it off. These are applications where
many small messages
are sent, and the time delays between the messages are maintained.
Application writers should not
set TCP_NODELAY unless the impact of doing so is well-understood and desired
because setting
TCP_NODELAY can have a significant negative impact on network and
application performance.

MaT

> -----Original Message-----
> From: hipster [mailto:hipster@xs4all.nl]
> Sent: Wednesday, September 26, 2001 11:28 AM
> To: ruby-talk ML
> Subject: [ruby-talk:21714] Re: Repost. Final call for help on
> this piece of code...
>
>
> On Wed, 26 Sep 2001  14:58:47 +0900, Hal E. Fulton wrote:
> [snip]
> in client, line ~64
>
> >     # Contact the server
> >
> >     socket = TCPSocket.new(ChessServer, ChessServerPort)
>
>       socket.setsockopt(Socket::SOL_TCP, Socket::TCP_NODELAY, 1)
>
> Would this be of any use? I'm not able to test this at the moment, but
> I can remember something similar where this came up as the solution.
>
>         HTH,
>         Michel
>