summaryrefslogtreecommitdiff
path: root/vendor/hyper/src/service/mod.rs
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/hyper/src/service/mod.rs')
-rw-r--r--vendor/hyper/src/service/mod.rs30
1 files changed, 0 insertions, 30 deletions
diff --git a/vendor/hyper/src/service/mod.rs b/vendor/hyper/src/service/mod.rs
deleted file mode 100644
index 28ffaddb..00000000
--- a/vendor/hyper/src/service/mod.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-//! Asynchronous Services
-//!
-//! A [`Service`] is a trait representing an asynchronous
-//! function of a request to a response. It's similar to
-//! `async fn(Request) -> Result<Response, Error>`.
-//!
-//! The argument and return value isn't strictly required to be for HTTP.
-//! Therefore, hyper uses several "trait aliases" to reduce clutter around
-//! bounds. These are:
-//!
-//! - `HttpService`: This is blanketly implemented for all types that
-//! implement `Service<http::Request<B1>, Response = http::Response<B2>>`.
-//!
-//! # HttpService
-//!
-//! In hyper, especially in the server setting, a `Service` is usually bound
-//! to a single connection. It defines how to respond to **all** requests that
-//! connection will receive.
-//!
-//! The helper [`service_fn`] should be sufficient for most cases, but
-//! if you need to implement `Service` for a type manually, you can follow the example
-//! in `service_struct_impl.rs`.
-
-mod http;
-mod service;
-mod util;
-
-pub use self::http::HttpService;
-pub use self::service::Service;
-pub use self::util::service_fn;