tokio_tower/pipeline/
mod.rs

1//! In a pipelined protocol, the server responds to client requests in the order they were sent.
2//! Many requests can be in flight at the same time, but no request sees a response until all
3//! previous requests have been satisfied. Pipelined protocols can experience head-of-line
4//! blocking wherein a slow-to-process request prevents any subsequent request from being
5//! processed, but are often to easier to implement on the server side, and provide clearer request
6//! ordering semantics. Example pipelined protocols include HTTP/1.1, MySQL, and Redis.
7//!
8//! Note: pipelining with the max number of in-flight requests set to 1 implies that for each
9//! request, the response must be received before sending another request on the same connection.
10
11/// Client bindings for a pipelined protocol.
12pub mod client;
13pub use self::client::Client;
14
15/// Server bindings for a pipelined protocol.
16pub mod server;
17pub use self::server::Server;
tokio_tower/pipeline/mod.rs

tokio_tower/pipeline/
mod.rs
