[−][src]Module hyper::body
Streaming bodies for Requests and Responses
For both Clients and Servers, requests and responses use streaming bodies, instead of complete buffering. This allows applications to not use memory they don't need, and allows exerting back-pressure on connections by only reading when asked.
There are two pieces to this in hyper:
- The
Payload
trait the describes all possible bodies. hyper allows any body type that implementsPayload
, allowing applications to have fine-grained control over their streaming. - The
Body
concrete type, which is an implementation ofPayload
, and returned by hyper as a "receive stream" (so, for server requests and client responses). It is also a decent default implementation if you don't have very custom needs of your send streams.
Structs
Body | A stream of |
Chunk | A piece of a message body. |
Sender | A sender half used with |
Traits
Payload | This trait represents a streaming body of a |