Crate nyquest_interface

Interface definitions for nyquest HTTP client backends.

This crate provides the interface that backends must implement to be compatible with the nyquest HTTP client facade. It defines the core types and traits that are used across all nyquest implementations.

Backend Registration

Backend implementations must register themselves using the register_backend function before they can be used by nyquest.

Features

• async: Enable async interface support
• blocking: Enable blocking interface support
• multipart: Enable multipart form support

Re-exports

pub use body::Body;

pub use body::Part;multipart

pub use body::PartBody;multipart

Modules

asyncasync

Asynchronous HTTP client interface.

blockingblocking

Blocking HTTP client interface.

body

Request body types for nyquest HTTP clients.

client

HTTP client configuration and building.

Structs

Request

Represents an HTTP request to be sent by a nyquest client.

Enums

Error

Common error types that can occur in nyquest HTTP operations.

Method

HTTP request methods supported by nyquest.

Functions

register_backend

Registers a backend implementation for use with nyquest.

Type Aliases

Result

Result type for nyquest HTTP operations.