Chris Baus

Updated TCP_CORK entry

I updated my TCP_CORK entry to emphasize using the gather function writev(). I previously gave it lower priority because of the buffer arithmetic it requires when using non-blocking I/O. This isn't reason enough not to use writev() when attempting to write multiple buffers that are currently in memory. It is cleaner than setting TCP_CORK, making multiple calls to write(), and then clearing TCP_CORK. Ok the API is ugly, but so is the entire socket API. As it stands right now we are stuck with it. I really should give TCP_NODELAY a section to itself as well.

If there is anybody still out there who could technically review the entry, I would appreciate it.