[En-Nut-Discussion] NutTcpAccept blocks the tread

[urbi]

I have to handel some different incomming TCP-connections in my application.
So I would like to have one thread that controls (sequently) all the
incoming connactions.

The function NutTcpAccept() is blocking the calling thread, so I have to
spend for each connection his own thread. In this way I have a lot of
unnecessary taskswitches and I block unnecessary Memory. 

Is there an other way (not blocking) for waiting for a connection (with an
Error-Message "no actual connection")?

thank you for any help, Urban
-- 
View this message in context: http://www.nabble.com/NutTcpAccept-blocks-the-tread-tp25791815p25791815.html
Sent from the MicroControllers - Ethernut mailing list archive at Nabble.com.