Struct ExternalClient 

pub struct ExternalClient { /* private fields */ }

External data source client

TLS crypto provider

When built with the download feature, ExternalClient::new / ExternalClient::with_config construct a reqwest::Client eagerly, which builds its rustls ClientConfig inside .build() even for a client that never issues an HTTPS request. Since the workspace’s reqwest dependency uses rustls-no-provider (no aws-lc-rs/ring bundled – see the “PURE RUST BLOCKER (reqwest)” note in the workspace root Cargo.toml), this crate installs the pure-Rust OxiTLS provider (oxitls-rustcrypto-provider, COOLJAPAN’s RUSTSEC-2026-0104-fixed fork of the abandoned upstream rustls-rustcrypto 0.0.2-alpha, resolved under the rustls-rustcrypto name) as the process-default rustls CryptoProvider automatically, right before the first client is constructed – unless the application has already installed a provider of its own. Applications that want a different provider (e.g. a C-linked aws-lc-rs/ring one) simply call rustls::crypto::CryptoProvider::install_default(...) before the first use of SciRS2 networking; an existing process default is never overridden.

Implementations

impl ExternalClient

pub fn new() -> Result<Self>

Create a new external client with default configuration

pub fn with_config(config: ExternalConfig) -> Result<Self>

Create a new external client with custom configuration

pub async fn download_dataset( &self, url: &str, progress: Option<ProgressCallback>, ) -> Result<Dataset>

Download a dataset from a URL

pub fn download_dataset_sync( &self, url: &str, progress: Option<ProgressCallback>, ) -> Result<Dataset>

Download a dataset synchronously (blocking) - when download feature is enabled