|Subject:||Re: [lwip-users] the sequentiality of the lwip stack|
|Date:||Wed, 19 Mar 2014 13:28:20 -0300|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130801 Thunderbird/17.0.8|
Em 19-03-2014 10:49, Pomeroy, Marty escreveu:
A common situation is to have one thread listening synchronously (blocking) and another task wants (for example, due to some error) to disconntinue the comunication and close that socket.
there are situations where different threads send and recieve, but I don't remember of any example.
but having each socket stick to it's thread if not a big problem... you just have to pool for new data and doing a task-delay
|[Prev in Thread]||Current Thread||[Next in Thread]|