On 11/17/22 20:34, Dan Inve wrote:
Hi Christian,
Sounds like you should be using MHD_create_response_from_iovec(). That
way, you can avoid the memcpy() entirely.
I took a look at MHD_create_response_from_iovec, but I'm not sure if that
works for my circumstance because it doesn't use a cal
Hi Christian,
Sounds like you should be using MHD_create_response_from_iovec(). That
> way, you can avoid the memcpy() entirely.
>
I took a look at MHD_create_response_from_iovec, but I'm not sure if that
works for my circumstance because it doesn't use a callback. The data from
the driver isn't
Dear Dan,
Sounds like you should be using MHD_create_response_from_iovec(). That
way, you can avoid the memcpy() entirely.
Happy hacking!
Christian
On 11/17/22 08:27, Dan Inve wrote:
Hi,
I'm using libmicrohttpd to respond to an HTTP request for a large amount of
data (sometimes GBs) using
Hi,
I'm using libmicrohttpd to respond to an HTTP request for a large amount of
data (sometimes GBs) using external select
and MHD_create_response_from_callback with a known size. The data is
sourced from hardware via a kernel driver. When the HTTP request is
received, data is requested from the h
Hi,
I'm using libmicrohttpd to respond to an HTTP request for a large amount of
data (sometimes GBs) using external select
and MHD_create_response_from_callback with a known size. The data is
sourced from hardware via a kernel driver. When the HTTP request is
received, data is requested from the h
