fetch 0.13.0

HTTP client with resilience, observability, and Tokio runtime support.
Documentation 
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

// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.

//! # HTTP Client Pooling Example
//!
//! By default, the HTTP client only supports a single HTTP/2 connection per host.
//! This can become a bottleneck when making many concurrent requests to the same endpoint.
//!
//! This example demonstrates how to work around this limitation by using multiple connection
//! pools. Each pool maintains its own HTTP/2 connection, allowing for better parallelism
//! and throughput when making concurrent requests.

use fetch::HttpClient;
use fetch::fake::FakeDeps;
use fetch::options::{ConnectionPoolOptions, PoolSelection};
use http::StatusCode;

#[path = "util/utils.rs"]
mod utils;

#[tokio::main]
async fn main() -> Result<(), ohno::AppError> {
    let client = HttpClient::builder_fake(StatusCode::OK, FakeDeps::default())
        .minimal_pipeline()
        .connection_pool_options(ConnectionPoolOptions::default().multiple_pools(10, PoolSelection::round_robin()))
        .build();

    for _ in 0..1000 {
        _ = client.get("https://example.com").fetch().await?;
    }

    println!("example finished");

    Ok(())
}