use TCP_NODELAY on TCP sockets?

[Marco d'Itri]

On May 15, Job Snijders via Bird-users <bird-users at network.cz> wrote:

> But please be very careful in considering this patch, because it does
> introduce some subtle changes in the on-the-wire behaviour of BIRD. For
> example, without this patch an UPDATE for a handful of routes and the
> End-of-RIB marker might end up in the same TCP packet (if this fits);
> but with this patch, the End-of-RIB marker ends up in its own TCP
> packet. As things are today, setting TCP_NODELAY will increase the
I think that this can be fixed easily with TCP_CORK.
Basically, with TCP_NODELAY + TCP_CORK you can have the optimal balance 
of latency and overhead without using writev.

-- 
ciao,
Marco