On Wed, 2008-11-26 at 13:00 +0100, Micael wrote: > Hi Guys, > > In my quest of mapping out/understanding the functionality and inner > workings of lwip, I have come to the 'thread awareness' part. > > I understand the code are written to use and care about threads, at least > with the netconn and socket interface, but to what extent? > > > 1. Can I, for instance, have multiple threads managing their own sockets? > i.e. can I do a http server as a thread, creating/using/closing while I > have another thread doing similar stuff on another port? > > 2. I guess that each socket in it self is not threadsafe; i.e. I cannot > create a listen thread, and another writing thread using the same socket. > ( this would surprise me, but I thought I should ask ;-) )
2 definitely won't work. 1 might work. Safest would be to direct all socket access through a single thread. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
