| aggregate.rs |
|
905 |
| body.rs |
wanter = |
24522 |
| length.rs |
|
3708 |
| mod.rs |
Streaming bodies for Requests and Responses
For both [Clients](crate::client) and [Servers](crate::server), 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 [`HttpBody`](HttpBody) trait** describes all possible bodies.
hyper allows any body type that implements `HttpBody`, allowing
applications to have fine-grained control over their streaming.
- **The [`Body`](Body) concrete type**, which is an implementation of
`HttpBody`, 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. |
2310 |
| to_bytes.rs |
|
2599 |