-
-
Notifications
You must be signed in to change notification settings - Fork 475
Description
Hi, I'm currently using Crow 1.2.0 in an embedded environment with C++14 support, and I'm trying to implement a file upload feature that supports large files (up to GB-level).
However, I noticed that the crow::request::body is returned as a std::string, which implies that the entire request body is read into memory at once. This behavior is problematic when dealing with large file uploads, as it may easily lead to OOM (Out of Memory) errors on resource-constrained embedded systems.
❓ My Questions:
Does Crow currently support streaming or chunked reading of the request body?
If not, are there any recommended workarounds or design patterns to implement streaming behavior manually?
Is there a plan to support asynchronous or stream-based request body handling in future versions?