hpx 2.4.7

High Performance HTTP Client
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

use std::sync::Arc;

use super::Req;

pub trait Scope: Send + Sync + 'static {
    fn applies_to(&self, req: &super::Req) -> bool;
}

// I think scopes likely make the most sense being to hosts.
// If that's the case, then it should probably be easiest to check for
// the host. Perhaps also considering the ability to add more things
// to scope off in the future...

// For Future Whoever: making a blanket impl for any closure sounds nice,
// but it causes inference issues at the call site. Every closure would
// need to include `: ReqRep` in the arguments.
//
// An alternative is to make things like `ScopeFn`. Slightly more annoying,
// but also more forwards-compatible. :shrug:

pub struct ScopeFn<F>(pub(crate) F);

impl<F> Scope for ScopeFn<F>
where
    F: Fn(&Req) -> bool + Send + Sync + 'static,
{
    fn applies_to(&self, req: &Req) -> bool {
        (self.0)(req)
    }
}

/// Defines the scope of requests that are eligible for retry.
#[derive(Clone)]
pub(crate) enum Scoped {
    /// All requests are eligible for retry regardless of their properties.
    Unscoped,
    /// Use custom logic to determine if a request is eligible for retry.
    Dyn(Arc<dyn Scope>),
}

impl Scoped {
    /// Checks if the given request falls within the retry scope.
    pub(super) fn applies_to(&self, req: &super::Req) -> bool {
        let ret = match self {
            Scoped::Unscoped => true,
            Scoped::Dyn(s) => s.applies_to(req),
        };
        trace!("retry in scope: {ret}");
        ret
    }
}