Struct viaduct::settings::Settings

#[non_exhaustive]pub struct Settings {
    pub read_timeout: Option<Duration>,
    pub connect_timeout: Option<Duration>,
    pub follow_redirects: bool,
    pub use_caches: bool,
}

Note: reqwest allows these only to be specified per-Client. concept-fetch allows these to be specified on each call to fetch. I think it's worth keeping a single global reqwest::Client in the reqwest backend, to simplify the way we abstract away from these.

In the future, should we need it, we might be able to add a CustomClient type with custom settings. In the reqwest backend this would store a Client, and in the concept-fetch backend it would only store the settings, and populate things on the fly.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

read_timeout: Option<Duration>

connect_timeout: Option<Duration>

follow_redirects: bool

use_caches: bool

Trait Implementations

impl Debug for Settings

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<Settings> for Settings

fn eq(&self, other: &Settings) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Settings) -> bool

This method tests for !=.

impl StructuralPartialEq for Settings