I don't think I follow you completely.
An HTTP server, like the one in lwIP, will let you build your user
interface. You can send data to the server and you can get data from the
server. The server can also be instructed to run some code of your own,
a CGI, when some URLs are requested. Whatever travels inside that "data"
is up to you.
In this implementation, there is no filesystem per se, but a helping
construction to serve static content and simple dynamic forms, in the
form of SSI tags. To serve entirely dynamic content like a video stream,
you'd be better off using CGIs. To have a full fledged file system, you
need to run something that provides it, and interface lwIP to that.
When serving, the server will send as much as he can providing the
content is ready when needed (e.g.: your CGI provides it), as long as
there is enough buffering space available. Then, the lwIP stack will
deliver that as best as it can, providing it is accepted by the netif
driver and the other end can handle that content, as this is TCP.
Perhaps to send that amount of traffic you'll need to trim your config.
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
