[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #6969] Review usage of conn->err in netconn layer

From: Frédéric Bernon
Subject: [lwip-devel] [task #6969] Review usage of conn->err in netconn layer
Date: Tue, 26 Jun 2007 17:38:58 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070515 Firefox/

Follow-up Comment #11, task #6969 (project lwip):

About comment#8, I should add that api_lib should never set conn->err in any
case (and should just read it). But about ERR_MEM, I'm not agree: if a
lwip_sendto operation doesn't get a pbuf or a buffer in the device to send a
datagram, it is an error (lwip_sendto should return -1), but not a "fatal"
one (the application can retry).

About comment#9 & comment#10, I think that tests like (pcb!=NULL) or
(mboxes!=NULL) are not good, since an err_tcp doesn't cause to free the pcb
or the mbox. But change the core to handle such cases is redundant with
conn->err, and more complex than solution propose in comment#1 & comment#2.


Reply to this item at:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]