Hi, Alex!
I am using this option for a long time in several situations
and I have not experienced any problem.
In every case, TCP_NODELAY has nothing in common with
blocking, non-blocking functionality. It is connected
to so-called "Nagle's Rule"(see linux/net/ipv4/tcp.c file)
> -----Original Message-----
> From: Aleksandar Bakic [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 19, 1999 11:58 AM
> To: Michael Frank
> Cc: RT-Linux Mailing List
> Subject: Re: [rtl] Networking With RT-Linux
>
>
> "Michael Frank" <[EMAIL PROTECTED]> writes:
>
> > The right option to make socket non-blocking one is
> >
> > fcntl(fd, F_SETFL, O_NONBLOCK)
>
> Hm... I actually used this in one application long time ago, but
> removed it because it behaved strangely. (Could be just that some data
> were lost due to lack of buffer space; the TCP_NODELAY seemed better,
> although I can't remember exactly what it does.)
>
> Thanks,
> Aleks
> --- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ----
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/~rtlinux/
>
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
