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

[Rishi Khan]

Why don't you just put mutexes around the appropriate code in the  
sockets library (if you're at that level) or the netconn library (if  
you're at that level).

On May 13, 2009, at 8:04 AM, ncoage wrote:

> Maybe I'm wrong, but my application can't work like you said. I  
> have 3 serial ports, if one port has just send data and now is  
> waiting for reply (several seconds), another can't be blocked. So I  
> must use seperate tasks for each serial port.
>
> When I receive data from tcp I have to get to know what is the  
> "address" of the target (slave device connected to serial port). I  
> have a image to show you how my application must work
> http://img217.imageshack.us/img217/4508/tcpser.jpg
> If I want something from device with address "3" I want to also  
> communicate with device with address "5" simultaneously without  
> need to wait until device "3" reply.
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users