On Sun, 2007-07-29 at 20:44 -0600, David Vos wrote: > Thanks for the explanation. I had read some old documentation > somewhere that suggested that lwip required you to handle resending > data yourself (the data due to lost packets). Now I see why this > function is useful in other ways.
Also, if the sending process has used the sort of pbuf that references memory directly rather than making the stack copy it, this callback lets them know that the stack will not reference the data any more and the sending process is free to do what it likes with it. Before this callback is called the stack could still need the data and so the application must ensure it remains valid. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
