File tree 6 files changed +13
-12
lines changed
6 files changed +13
-12
lines changed Original file line number Diff line number Diff line change 7
7
//!
8
8
//! There are two pieces to this in hyper:
9
9
//!
10
- //! - The [`Payload`](Payload) trait the describes all possible bodies. hyper
10
+ //! - The [`Payload`](body:: Payload) trait the describes all possible bodies. hyper
11
11
//! allows any body type that implements `Payload`, allowing applications to
12
12
//! have fine-grained control over their streaming.
13
13
//! - The [`Body`](Body) concrete type, which is an implementation of `Payload`,
Original file line number Diff line number Diff line change @@ -6,7 +6,7 @@ use super::internal::{FullDataArg, FullDataRet};
6
6
7
7
/// This trait represents a streaming body of a `Request` or `Response`.
8
8
///
9
- /// The built-in implementation of this trait is [`Body`](Body), in case you
9
+ /// The built-in implementation of this trait is [`Body`](:: Body), in case you
10
10
/// don't need to customize a send stream for your own application.
11
11
pub trait Payload : Send + ' static {
12
12
/// A buffer of bytes representing a single chunk of a body.
Original file line number Diff line number Diff line change 2
2
//!
3
3
//! This module contains:
4
4
//!
5
- //! - A [`GaiResolver`](GaiResolver) that is the default resolver for the
5
+ //! - A [`GaiResolver`](dns:: GaiResolver) that is the default resolver for the
6
6
//! `HttpConnector`.
7
- //! - The [`Resolve`](Resolve) trait and related types to build a custom
7
+ //! - The [`Resolve`](dns:: Resolve) trait and related types to build a custom
8
8
//! resolver for use with the `HttpConnector`.
9
9
use std:: { fmt, io, vec} ;
10
10
use std:: error:: Error ;
Original file line number Diff line number Diff line change 3
3
//! There are two levels of APIs provided for construct HTTP clients:
4
4
//!
5
5
//! - The higher-level [`Client`](Client) type.
6
- //! - The lower-level [conn]( conn) module.
6
+ //! - The lower-level [` conn`](client:: conn) module.
7
7
//!
8
8
//! # Client
9
9
//!
Original file line number Diff line number Diff line change 6
6
//! There are two levels of APIs provide for constructing HTTP servers:
7
7
//!
8
8
//! - The higher-level [`Server`](Server) type.
9
- //! - The lower-level [conn]( conn) module.
9
+ //! - The lower-level [` conn`](server:: conn) module.
10
10
//!
11
11
//! # Server
12
12
//!
Original file line number Diff line number Diff line change 1
1
//! Services and MakeServices
2
2
//!
3
- //! - A [`Service`](Service) is a trait representing an asynchronous function
4
- //! of a request to a response. It's similar to
3
+ //! - A [`Service`](service:: Service) is a trait representing an asynchronous
4
+ //! function of a request to a response. It's similar to
5
5
//! `async fn(Request) -> Result<Response, Error>`.
6
- //! - A [`MakeService`](MakeService) is a trait creating specific instances of a
7
- //! `Service`.
6
+ //! - A [`MakeService`](service:: MakeService) is a trait creating specific
7
+ //! instances of a `Service`.
8
8
//!
9
9
//! These types are conceptually similar to those in
10
10
//! [tower](https://crates.io/crates/tower), while being specific to hyper.
16
16
//! connection will receive.
17
17
//!
18
18
//! While it's possible to implement `Service` for a type manually, the helpers
19
- //! [`service_fn`](service_fn) and [`service_fn_ok`](service_fn_ok) should be
20
- //! sufficient for most cases.
19
+ //! [`service_fn`](service::service_fn) and
20
+ //! [`service_fn_ok`](service::service_fn_ok) should be sufficient for most
21
+ //! cases.
21
22
//!
22
23
//! # MakeService
23
24
//!
You can’t perform that action at this time.
0 commit comments