Re: [lwip-users] Handling ERR_MEM from tcp_close()

2016-11-18 Thread Simon Goldschmidt
Sergio R. Caprile wrote: > I use an extra CLOSING state, so the poll callback can kick in. > When closing, if close succeeds, state is CLOSED and everybody is happy. > Otherwise, state is CLOSING and the poll callback will retry. While discussing bug #47485, we kind of decided that it would be

Re: [lwip-users] Handling ERR_MEM from tcp_close()

2016-11-18 Thread Sergio R. Caprile
Too much code, I won't look at it. From the wiki: http://lwip.wikia.com/wiki/Raw/TCP "The function may return ERR_MEM if no memory was available for closing the connection. If so, the application should wait and try again either by using the acknowledgment callback or the polling

[lwip-users] Handling ERR_MEM from tcp_close()

2016-11-16 Thread Longin Kandinsky
Hello, I'm developing specific TCP server using RAW LwiP 1.41 and I have some doubts about understanding closing connection. My TCP server should have only one active client per bound port. If new client comes (tcp_accept callback with new pcb) the old one should be shut down. Here is the part