tokio_tower/pipeline/
mod.rs

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

/// Client bindings for a pipelined protocol.
pub mod client;
pub use self::client::Client;

/// Server bindings for a pipelined protocol.
pub mod server;
pub use self::server::Server;