WIP: Request body serializer

[abhilashraju]

bmcweb changes for serialising request body into file
Signed-off-by: Abhilash Raju [email protected]

[baemyung]

This seems putting the request body into a file - which seems good for the given purpose.
However, I'm wondering how body() function will be handled as it becomes empty for this route.

bmcweb uses body() in many places.
How can we make sure not to use it in this path?

Perhaps, can this feature be enabled by an meson option, and/or by a dynamic option (as a part of Request header)?
Also, going through upstream community first?

[abhilashraju]

This seems putting the request body into a file - which seems good for the given purpose. However, I'm wondering how body() function will be handled as it becomes empty for this route.

bmcweb uses body() in many places. How can we make sure not to use it in this path?

Perhaps, can this feature be enabled by an meson option, and/or by a dynamic option (as a part of Request header)? Also, going through upstream community first?

Serialization is not applied by default. You can refer to the update service route registration handler to see how serialization is enabled for a specific URL. In these cases, the handler chooses to stream the request body directly into a file, so it does not use the body() call on the request object. By default, all other handlers read the body into a string as usual.