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

[Simon Goldschmidt]

I didn't want to tell you how to write the serial part, however, the connection 
to lwIP stays the same: assemble a packet for serial either in netconn-recv or 
raw-API recv-callback and put it on a queue to the correct serial task.

The problem you then have is you need to know the correct pcb (or netconn) to 
answer to (if there is an answer). That problem is the same, regardless of the 
API used for lwIP.

The only advantage of the raw API over the netconn API is you save a thread.

Simon


> 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

-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss 
für nur 17,95 Euro/mtl.!* 
http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a