* feat: response body memstream
* feat: auto_buf response header
* chore: format nit
* feat: request memstream
* removed zombie http-req-size from README files
* fix panic typos
* Update parser structure with the new http_body start address when buffer is moved by memstream
* fix case when header_length is zero at the beginning
Co-authored-by: emil <emil916@gmail.com>
* Async I/O is being used for reading and writing http request and
response respectively. This causes the worker core to steal new tasks as
when one sandbox blocks on "read" or "write". This causes true
round-robin on timer interrupts, leading to those high latencies.
* Ideally, the request/response should be synchronous I belive because
we are expected to have "low"/near-realtime latencies and the read/writes
are only performed when a client connects, so ideally not block!
Plus, we expect only small data transfers (in KBs) so that should also
support synchronous request/response processing.
Sean McBride
phani