Skip to main content

Crate taba_client

Crate taba_client 

Source
Expand description

The Taba Rust connector (doc 19): the nine operations of the client API, the common contract’s call retries and its own HTTP/1.1 over std::net::TcpStream, with rustls for TLS.

Re-exports§

pub use client::Call;
pub use client::Client;
pub use client::Config;
pub use client::ConsumeError;
pub use client::ConsumeOptions;
pub use client::Delivery;
pub use client::Error;
pub use client::HandlerError;
pub use client::Message;
pub use client::Nullable;
pub use client::Page;
pub use client::PublishOptions;
pub use client::PublishResponse;
pub use client::Reply;
pub use client::Topic;
pub use client::TopicRequest;
pub use client::TopicUpdate;
pub use client::VisibilityResponse;
pub use client::CONTRACT_VERSION;

Modules§

base64
Standard Base64 (RFC 4648), our own: the connector depends on no library for this.
client
The client: the configuration, the call with the common contract’s retries (doc 19, section 18.4) and the nine operations of the surface (section 18.3).
http
HTTP/1.1 as pure functions, with no input or output (doc 19a, section 18.10.3): building the request, interpreting the response (Content-Length, chunked or until the connection ends) and reading the address. The transport (TCP, TLS) only carries bytes back and forth.
json
Minimal JSON reader (doc 19, section 18.5).
transport
The transport: carries the request bytes to the server and brings the response back. The core (building and reading HTTP) is in http; here there is only TCP and TLS (rustls, TLS 1.2 or later).