docs.rs failed to build pb-mapper-0.6.1
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

Visit the last successful build: pb-mapper-0.5.2

pb-mapper

Client SDK for a deployed pb-mapper relay.

pb-mapper = "0.6.1"

use pb_mapper::{Client, ClientConfig, RegisterRequest, Transport};

# async fn example() -> pb_mapper::Result<()> {
let client = Client::new(ClientConfig {
    server: "relay.example.com:7666".into(),
    credential: "0123456789abcdefghijklmnopqrstuv".into(),
    keep_alive: true,
    namespace: None,
})?;

let registration = client
    .register(RegisterRequest {
        key: "echo".into(),
        local_addr: "127.0.0.1:8080".into(),
        transport: Transport::Tcp,
        codec: false,
        force_namespace: false,
    })
    .await?;
registration.wait_ready().await?;
registration.stop().await?;
# Ok(())
# }

Requires a Tokio runtime. The unified CLI is a separate package (pb-mapper-cli).

For TCP services with application heartbeats, use client.register_with_idle_timeout(request, std::time::Duration::from_secs(90)) to reclaim abandoned data connections on the publisher. Activity in either direction resets the deadline; Duration::ZERO disables it. UDP is rejected. Ordinary register calls, other registrations, and control connections keep their existing behavior. No relay or subscriber upgrade is required.

pb-mapper 0.6.1

pb-mapper