GitXplorerGitXplorer
a

vertx-eventbus-client-rs

public
10 stars
2 forks
4 issues

Commits

List of commits on branch master.
Unverified
2a8391d48f177d8ec9daaf9e2e973cb9d3502634

fix public issue

committed 4 years ago
Unverified
d1a501806c0ada81ea4403e08e78f4d92f6b7e03

fix public issue

committed 4 years ago
Verified
ce0f40ee5c9fb5939159097273863bb54e20c898

Merge pull request #13 from aesteve/feat/pub-mods

aaesteve committed 4 years ago
Unverified
558a98f41af328d7ea935aa7ae04b6f57e5d6687

pub modules

committed 4 years ago
Verified
f0a56ded60021d5a99e4cce318cae923d8812f82

Merge pull request #12 from aesteve/dependabot/cargo/buffered-reader-0.20.0

aaesteve committed 4 years ago
Verified
03b51575bf46f47fcc2cc4bbdc9099f65211d9a2

Update buffered-reader requirement from 0.17.0 to 0.20.0

ddependabot[bot] committed 4 years ago

README

The README file for this repository.

License Crates.io Version codecov

Vert.x TCP EventBus client for Rust

Vert.x allows to expose its event-bus through a TCP socket. This crate offers primitives in the Rust programming language to interact with the event bus over this TCP connection.

This allows to send messages from a Rust codebase (embedded sensors for instance) to a running Vert.x instance, or reacting to event bus messages published from the Vert.x application in a Rust codebase.

Early stage

This project is still in early development phase, although it's available as a crate if you need it. The design (at the moment: iterators over incoming messages) is highly suggest to change.

Any proposition or technical comment is highly welcomed in the issues.

Testing

In order to test the client against a "real" TCP Event-Bus bridge (and avoid observator-bias: testing my own understanding of the protocol), this docker image is used, through testcontainers. The code for this image can be found here, it's a simple Vert.x application listening/publishing to the Event-Bus and exposing it through TCP on port 7542.