Re: [lwip-users] Issue with TCP raw API and messages larger than TCP_MSS

[David Perlaza]

Hi Simon,

Thank you for your email. 

My application currently copies the data in the pbuf into a larger buffer
every time the callback is called. When the TCP connection is closed by the
HTTP server after sending all the image data, I process this buffer as this
event marks the end of the HTTP data transfer. 

Best regards,

David.




-----Original Message-----
From: lwip-users
[mailto:address@hidden On Behalf Of
Simon Goldschmidt
Sent: Monday, 10 April 2017 5:18 PM
To: address@hidden
Subject: Re: [lwip-users] Issue with TCP raw API and messages larger than
TCP_MSS

David Perlaza wrote:
> Am I missing any configuration settings to enable the buffering of the
entire HTTP data before it gets processed in my tcp_recv callback?

There's no such thing. Your application must be prepared to receive pbufs as
they are received from the wire. The only exception is packet loss, where
mulitple packets are combined sometimes.
This is a callback API!
Keeping that aside, how do you expect the stack (TCP/IP!) would know when
the HTTP data is done??

Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users