🚀 go-pugleaf

"Robert G. Hoover" <not.a.real.address@anywhere.sorry> wrote in message
news:43627188@newsgroups.borland.com...

> I've traced this lag to "whatever happens after
TCustomWinSocket::SendBuf()".

SendBuf() calls the winsock API send() function.  By default, a socket will
buffer outgoing data and not send it immediately.  This allows the socket to
send efficient packets.  This is known as "send coalescing", also known as
the Nagle algorithm.  Have a look at the socket API setsockopt() function
for details on the TCP_NODELAY option.

> I tried to call Application->ProcessMessages() to force windows
> to process the sending event immediately, but it had no effect.
> My assumption is that the SendBuf command posts the event
> message to Windows

Your assumptions is not correct.  Socket writes do not use window messages
at all.  Calling ProcessMessages() has no effect on an outgoing socket
transmission, other than to slow down the code that surrounds the writing.

> Windows doesn't get around to actually sending bytes across the
> LAN cable for 2 seconds.

That is a very likely possibility.

> Is there a way to kick Windows in the pants to process my event
> immediately?

See above.


Gambit