1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
use ;
use http;
use ;
/// A `Responder` is any type which is returned from a request [`Handler`].
///
/// This trait exists so that the ergonomics of writing [`Handler`] functions are nicer, as they can
/// return an `impl Responder` type, which is automatically inferred based on the body of the
/// function.
///
/// The `Responder` trait is automatically implemented for any type which implements:
///
/// ```ignore
/// IntoFuture<Item = http::Response<impl Body>, Error: impl Into<aitch::Error>>
/// ```
///
/// Importantly, this means it is implemented for the following types:
///
/// - `http::Result<http::Reponse<impl Body>>`, which is the result of calling
/// `http::response::Builder::body(...)` inside of a [`Handler`].
/// - A [`Future`] which eventually yields a `http::Response<impl Body>`.
///
/// As this implementation is done through a blanket impl for any `T`, it is unlikely that
/// downstream crates will be able to implement `Responder` for any custom types. Downstream crates
/// should instead ensure that their types implement `IntoFuture` (with the appropriate
/// constraints), to ensure that they can make use of the `Responder` impl provided by aitch.
///
/// [`Handler`]: trait.Handler.html
/// [`Future`]: https://docs.rs/futures/0.1.23/futures/future/trait.Future.html
// TODO: See if we can get rid of the `BoxedResponse` and instead return a static type. Simple
// experiments showed this to be somehow slower?