battler-wamprat

Crates.iobattler-wamprat
lib.rsbattler-wamprat
version
sourcesrc
created_at2025-01-01 20:26:41.136609+00
updated_at2025-04-24 20:48:55.910178+00
descriptionAsynchronous library for strongly-typed WAMP peer messaging.
homepage
repositoryhttps://github.com/jackson-nestelroad/battler/tree/main/battler-wamprat
max_upload_size
id1501064
Cargo.toml error:TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
Jackson Nestelroad (jackson-nestelroad)

documentation

README

battler-wamprat

battler-wamp + RaT (Reconnection and Typing)

Latest Version

battler-wamprat is a Rust library and framework for peers communicating over the Web Application Message Protocol (WAMP).

The library is built on battler-wamp to provide more complex functionality:

  1. Strongly-typed procedure handling, procedure calls, event publication, and subscription event handling using built-in serialization and deserialization.
  2. Automatic reconnection and re-registration of procedures and subscriptions when a session is dropped.

The library uses tokio as its asynchronous runtime, and is ready for use on top of WebSocket streams.

What is WAMP?

WAMP is an open standard, routed protocol that provides two messaging patterns: Publish & Subscribe and routed Remote Procedure Calls. It is intended to connect application components in distributed applications. WAMP uses WebSocket as its default transport, but it can be transmitted via any other protocol that allows for ordered, reliable, bi-directional, and message-oriented communications.

The WAMP protocol specification is described at https://wamp-proto.org/spec.html.

Commit count: 0

cargo fmt