The wiki page is indeed very confusing. I recently added some lines to rawapi.txt, but that new version is only available through CVS, yet.
The baseline is that what you are doing is not really supported: sockets AND netconns are not allowed to be shared between multiple threads. This is a known limitation (e.g. fullduplex protocols which read in one thread and write in another thread are not supported), but it's yet unclear if this will be changed. In your application, it could be enough if you just put the netconn on the queue and mark it as 'to be deleted' somehow, and delete it in the task that previously used it. Simon > Hi, > > I'm using netconn API with callback function. In callback function I check > the parameter len - if is greater than zero, I put a pointer to the > netconn to queue. Another task reads the queue and use that netconn to parse > data > and send reply. This operation may takes several seconds. What if callback > function will be called with parameter len equal zero? I know I must > delete netconn, but another task may be using that netconn to send reply. I > found some informations about that here > http://lwip.wikia.com/wiki/LwIP_and_multithreading, but they dont explain all > my doubts, or maybe I didnt > understand them. > > Regards, > Gregory > > > _______________________________________________ > lwip-users mailing list > [email protected] > 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 _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
