Closed
Description
We temporarily renamed the old hyper::Body
struct to hyper::body::Recv
in #2966. That was to unblock #2839, since we wanted to use the name for the trait instead. But, the name should be properly considered.
The purpose of this type is: an implementation of Body
to represent bodies received from a remote. So, the client side would see this in the Response
, and the server side would see this in the Request
. It is not meant to be constructed by users as a "default" implementation.
Some names I've seen or considered before:
Recv
RecvStream
/RecvBody
Streaming
Incoming
Remote
Wire
/FromWire
It might help to envision the type signature users will frequently see it as, such as Request<Streaming>
(or insert any other name in there).