Think your patch is a bit backwards.
>From MSDN:
TCP_NODELAY - Disables the Nagle algorithm for send coalescing.

So why does setting CURL_NAGLE turn TCP_NODELAY on? If Nagle is on, it means
TCP_NODELAY isn't. Same for CURLOPT_NAGLE. Setting CURLOPT_NAGLE = 1 should
not turn TCP_NODELAY on, it should turn it off. It seems confusing to me the
way you have it now...

Also, I would guess this probably needs some #ifdef'ing. Is this something
that every OS has? It seems to me putting it in a #ifdef TCP_NODELAY would
probably be the safest bet.

Dominick Meglio

----- Original Message -----
From: "Joe Halpin" <j.p.h_at_comcast.net>
To: "libcurl development" <curl-library_at_cool.haxx.se>
Sent: Sunday, March 21, 2004 2:19 PM
Subject: Re: TCP_NODELAY

> Daniel Stenberg wrote:
> > On Thu, 18 Mar 2004, Seshubabu Pasam wrote:
> >
> >
> >>Is it possible to get a handle to the write socket after the connect. I
am
> >>interested in setting the TCP_NODELAY option on the socket.
> >
> >
> > No, there's currently no such option. I wouldn't mind seeing this
offered
> > somehow...
> >
>
> Here's one possiblity.
>
> Joe
>
>
Received on 2004-03-21