On Tue, 2009-11-03 at 23:39 -0500, Dmitri Snejko wrote: > > > Hello Kieran, > > I have found the reason why the closed connection was missed with > receiving timeout set to 0. It was my application problem. The remote > side application was closed and windows stack sent RST. Netconn_recv set > err to ERR_RST. My application tried to close the netconn calling > netconn_close, netconn_delete. Netconn_close nether returned back > frizzing the receiving task.
That sounds like a bug. Could you file a bug report on savannah? > I removed netconn_close and left only > netconn_delete, never missed ERR_RST or ERR_CLSD any more. > For timeout set >0 lwip is still missing closed connections but it > could be the racing you mentioned. I found the all idea doesn't work > well and the application should follow sockets select way to be really > nonblocking on multiple netconns. That is the easiest way. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
