On Mon, 30 May 2005, David Laight wrote:
> In particular  the PSH flag isn't exposed to the application itself by
> any APIs I know of.  So the application cannot use it to pervert the
> cause of Nagle on a per-send basis.

I kind of expected that writes without fflush() or equivalent would not
set the TCP PSH flag.  Apparently I was wrong about that.

Nevertheless, could we use fflush() to tell TCP to send buffered data
without waiting for Nagle-induced delays?

--apb (Alan Barrett)