Struct cargo::sources::registry::http_remote::HttpRegistry

pub struct HttpRegistry<'cfg> {

    index_path: Filesystem,
    cache_path: Filesystem,
    source_id: SourceId,
    config: &'cfg Config,
    url: Url,
    multi: Multi,
    requested_update: bool,
    downloads: Downloads<'cfg>,
    multiplexing: bool,
    fresh: HashSet<PathBuf>,
    fetch_started: bool,
    registry_config: Option<RegistryConfig>,
    auth_required: bool,
    login_url: Option<Url>,
    auth_error_headers: Vec<String>,
    quiet: bool,
}

A registry served by the HTTP-based registry API.

This type is primarily accessed through the RegistryData trait.

HttpRegistry implements the HTTP-based registry API outlined in RFC 2789. Read the RFC for the complete protocol, but roughly the implementation loads each index file (e.g., config.json or re/ge/regex) from an HTTP service rather than from a locally cloned git repository. The remote service can more or less be a static file server that simply serves the contents of the origin git repository.

Implemented naively, this leads to a significant amount of network traffic, as a lookup of any index file would need to check with the remote backend if the index file has changed. This cost is somewhat mitigated by the use of HTTP conditional fetches (If-Modified-Since and If-None-Match for ETags) which can be efficiently handled by HTTP/2.

Fields

index_path: Filesystem

Path to the registry index ($CARGO_HOME/registry/index/$REG-HASH).

To be fair, HttpRegistry doesn’t store the registry index it downloads on the file system, but other cached data like registry configuration could be stored here.

cache_path: Filesystem

Path to the cache of .crate files ($CARGO_HOME/registry/cache/$REG-HASH).

source_id: SourceId

The unique identifier of this registry source.

config: &'cfg Config

url: Url

Store the server URL without the protocol prefix (sparse+)

multi: Multi

HTTP multi-handle for asynchronous/parallel requests.

requested_update: bool

Has the client requested a cache update?

Only if they have do we double-check the freshness of each locally-stored index file.

downloads: Downloads<'cfg>

State for currently pending index downloads.

multiplexing: bool

Does the config say that we can use HTTP multiplexing?

fresh: HashSet<PathBuf>

What paths have we already fetched since the last index update?

We do not need to double-check any of these index files since we have already done so.

fetch_started: bool

Have we started to download any index files?

registry_config: Option<RegistryConfig>

Cached registry configuration.

auth_required: bool

Should we include the authorization header?

login_url: Option<Url>

Url to get a token for the registry.

auth_error_headers: Vec<String>

Headers received with an HTTP 401.

quiet: bool

Disables status messages.

Implementations

impl<'cfg> HttpRegistry<'cfg>

pub fn new( source_id: SourceId, config: &'cfg Config, name: &str ) -> CargoResult<HttpRegistry<'cfg>>

Creates a HTTP-rebased remote registry for source_id.

• name — Name of a path segment where .crate tarballs and the registry index are stored. Expect to be unique.

fn handle_http_header(buf: &[u8]) -> Option<(&str, &str)>

Splits HTTP HEADER: VALUE to a tuple.

fn start_fetch(&mut self) -> CargoResult<()>

Setup the necessary works before the first fetch gets started.

This is a no-op if called more than one time.

fn handle_completed_downloads(&mut self) -> CargoResult<()>

Checks the results inside the HttpRegistry::multi handle, and updates relevant state in HttpRegistry::downloads accordingly.

fn full_url(&self, path: &Path) -> String

Constructs the full URL to download a index file.

fn is_fresh(&self, path: &Path) -> bool

Check if an index file of path is up-to-date.

The path argument is the same as in RegistryData::load.

fn config_cached(&mut self) -> CargoResult<Option<&RegistryConfig>>

Get the cached registry configuration, if it exists.

fn config(&mut self) -> Poll<CargoResult<&RegistryConfig>>

Get the registry configuration from either cache or remote.

fn add_sleepers(&mut self) -> CargoResult<()>

Moves failed Downloads that are ready to retry to the pending queue.

Trait Implementations

impl<'cfg> RegistryData for HttpRegistry<'cfg>

fn prepare(&self) -> CargoResult<()>

Performs initialization for the registry.

fn index_path(&self) -> &Filesystem

Returns the path to the index.

fn assert_index_locked<'a>(&self, path: &'a Filesystem) -> &'a Path

Validates that the global package cache lock is held.

fn is_updated(&self) -> bool

Is the local cached data up-to-date?

fn load( &mut self, _root: &Path, path: &Path, index_version: Option<&str> ) -> Poll<CargoResult<LoadResponse>>

Loads the JSON for a specific named package from the index.

fn config(&mut self) -> Poll<CargoResult<Option<RegistryConfig>>>

Loads the config.json file and returns it.

fn invalidate_cache(&mut self)

Invalidates locally cached data.

fn set_quiet(&mut self, quiet: bool)

If quiet, the source should not display any progress or status messages.

fn download(&mut self, pkg: PackageId, checksum: &str) -> CargoResult<MaybeLock>

Prepare to start downloading a .crate file.

fn finish_download( &mut self, pkg: PackageId, checksum: &str, data: &[u8] ) -> CargoResult<File>

Finish a download by saving a .crate file to disk.

fn is_crate_downloaded(&self, pkg: PackageId) -> bool

Returns whether or not the .crate file is already downloaded.

fn block_until_ready(&mut self) -> CargoResult<()>

Block until all outstanding Poll::Pending requests are Poll::Ready.

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 720 bytes