Content-Type: multipart/related; type="multipart/alternative";
boundary="----_=_NextPart_001_01C6ED32.132CF677"
content-class: urn:content-classes:message
Hi Tom,
Which API do you use ? sockets or raw api ? If you use sockets API, I can suggest a little patch to fix this problem in lwip_close.
Hello Frédéric,
Can you post the lwip_close patch here? I'm very interested to see what it is.
Kind regards,
Clive Wilson
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
