[En-Nut-Discussion] Non-blocking NutTcpReceive()?

[Mike Baverso]

If I'm not mistaken setting 0ms timeout is the default
and this will block until an error or something is received.


----- Original Message ----- 
From: "Stephen Noftall" <stephenn at lcsaudio.com>
To: <en-nut-discussion at egnite.de>
Sent: Thursday, January 30, 2003 12:31 PM
Subject: [En-Nut-Discussion] Non-blocking NutTcpReceive()?


Hello;

I got my Ethernut board running, wow, I am very impressed! Just one problem
with a solder joint, and it's up and pinging now ;-)

I have a question about non-blocking TCP calls. Is there anyway to make
NutTcpReceive() non-blocking? I was going to call NutTcpSetSockOpt() with 0
mS timeout, will that do? I see in the code it will still switch to another
task if one is ready. I think this will be ok, but is there anyway to make
it return back with 0, and not switch tasks?

Stephen Noftall


_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo/en-nut-discussion