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
58
59
60

#![forbid(unsafe_code)]
#![deny(
    clippy::dbg_macro,
    missing_copy_implementations,
    rustdoc::missing_crate_level_docs,
    missing_debug_implementations,
    missing_docs,
    nonstandard_style,
    unused_qualifications
)]

/*!
trillium client is a http client that uses the same `conn` approach as
[`trillium`](https://trillium.rs) but which can be used
independently for any http client application.

## Connector

[`trillium_client::Client`] is built with a Connector. Each runtime crate
([`trillium_smol`](https://docs.trillium.rs/trillium_smol),
[`trillium_tokio`](https://docs.trillium.rs/trillium_tokio),
[`trillium_async_std`](https://docs.trillium.rs/trillium_tokio)) offers
a Connector implementation, which can optionally be combined with a
tls crate such as
[`trillium_rustls`](https://docs.trillium.rs/trillium_rustls) or
[`trillium_native_tls`](https://docs.trillium.rs/trillium_native_tls).

See the documentation for [`Client`] and [`Conn`] for further usage
examples.

*/

mod conn;
pub use conn::{Conn, UnexpectedStatusError, USER_AGENT};

#[cfg(feature = "json")]
pub use conn::ClientSerdeError;

mod pool;
// open an issue if you have a reason for pool to be public
pub(crate) use pool::Pool;

mod client;
pub use client::Client;

pub use trillium_http::{
    Error, HeaderName, HeaderValue, HeaderValues, Headers, KnownHeaderName, Result, Status, Version,
};

mod util;

pub use trillium_server_common::{async_trait, Connector, Url};

/// constructs a new [`Client`] -- alias for [`Client::new`]
pub fn client(connector: impl Connector) -> Client {
    Client::new(connector)
}

mod into_url;
pub use into_url::IntoUrl;