Re: [lwip-users] How to know if a full packed was ACK'ed ? (netconn api)

[Yann Suisini]

Currently , I use a TCP/IP with a APMI that looks like the lwip raw API. For
my software I wrote a little layer interfaced with my RTOS in order to get a
pseudo like sequential api. But the lwip one is better :-)
But a timeout / wait for acked on data sent is missing :( 

With raw API , I guess it's possible within the tcp_sent callback ?
So maybe I could add some code in the sequential api to call the netconn
callback when data are fully acked ?
But I really don't know if it's possible and if it could be done easily .

Yann.



Simon Goldschmidt wrote:
> 
> Yann Suisini wrote:
>> I want to use the netconn_api for my app , but I have a question :
>> I need to optimize the bandwith due to high latency connection
>> (intercontinental) , so I'll send big packets 
>> (about 5KB by 5KB) .
> That doesn't result in big packets: the data will be splitted into 
> multiple packets of 1460 bytes of data.
>>  Because the systeme doe not havo much memory I would 
>> send the data with NETCONN_NOCOPY . 
>> So I have to be sure the full packet was ACK to be able to use the netbuf
>> again . 
>> How can I know if the full packet was ACKed byt the remote peer ?
> With the netconn api, I think there's no way to tell. With the raw api, 
> your sent-callback would be called with the amount of bytes acked by the 
> peer, but the raw api is a little harder to use than the netconn api.
> 
> Simon
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-know-if-a-full-packed-was-ACK%27ed---%28netconn-api%29-tp25731642p25746081.html
Sent from the lwip-users mailing list archive at Nabble.com.