Hi Sergio,
Thank you for your email.
As I mentioned in my original post, I am using the raw API and the image
data is around 7 kB in size. As you mentioned in your message, I copy the
data in the pbuf into a larger buffer every time the callback is called.
This continues until the connection is
Imagine your image data is 3MB. Would you expect lwIP to buffer that on
a 32KB microcontroller ? No, would you ?
Right, that is, light-weight IP.
The server will send bytes as it wants.
TCP will send bytes as it wants.
They will be put in IP and sent via Ethernet
Each frame gets IP extracted,
You seem to have many thinks mixed up, and a lot of documents to read.
Your application will depend on three software players:
- the TCP/IP stack: lwIP
- Here, on this list, after you read all the documentation and have
something to ask which is a bit more specific than "how do I get my work
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
Hi,
I am currently writing a raw-API-based HTTP client to request and receive a
still image from an IP camera. The HTTP response from the camera is about 7
kB in size, and because of the fact the image is in the JPEG format, the
size of the message varies between messages. The problem I am
