> That has its advantages: it's a very local thing, and doesn't need any
> state. However, the fact is that you _need_ the persistency of a socket
> option if you want to take advantage of external programs etc getting good
> behaviour without having to know that they are talking to a socket.
*nod*
We set TCP_CORK on the socket we handed to external programs that were
being run via 'site exec' in an ftp server. It resulted in much nicer
packets being spit out, especially in the 'ls' case where it likes to
write() on really goofy boundaries.
[yes, ftp and 'site exec' in particular are far from sexy, but do the same
with CGI scripts and the world might care :)]
- z
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/