Re: [lwip-users] netconn - using in different tasks

[Kieran Mansley]

On Wed, 2009-05-13 at 10:52 +0200, ncoage wrote:
> > The simplest way of dealing with the len=0 case would be to still put
> > the netconn on your queue, together with some state that will allow the
> > other task to know that this connection should be closed, and get the
> > other task to delete it.
> 
> I thought about that solution, but my application is more complex.
> There are three tasks, each of them communicates with his own serial
> port. When new data come from TCP, I check specific flag, which
> determines wich task (serial port) must get rest of the data frame. 

Where do you get this flag from?

> Another question: what if I get (in callback function) parameter len = 0 and 
> ignore it? 

You'll run out of connections as they'll never get closed.

Kieran