#zmq #zeromq #futures #tokio

tokio-zmq

Provides Futures abstractions for ZeroMQ on the Tokio event-loop

19 releases (8 breaking)

0.10.1 Jun 18, 2019
0.9.0 Dec 23, 2018
0.8.0 Nov 16, 2018
0.4.0-beta3 Apr 6, 2018
0.4.0-beta Mar 25, 2018

#211 in Asynchronous

Download history 56/week @ 2020-11-02 51/week @ 2020-11-09 33/week @ 2020-11-16 98/week @ 2020-11-23 66/week @ 2020-11-30 70/week @ 2020-12-07 25/week @ 2020-12-14 30/week @ 2020-12-21 31/week @ 2020-12-28 36/week @ 2021-01-04 32/week @ 2021-01-11 60/week @ 2021-01-18 32/week @ 2021-01-25 27/week @ 2021-02-01 75/week @ 2021-02-08 70/week @ 2021-02-15

261 downloads per month
Used in 3 crates (2 directly)

GPL-3.0 license

93KB
1.5K SLoC

Tokio ZMQ

This readme is for the 0.8 branch, for the 0.3 readme, look here

documentation crates.io

This crate contains wrappers around ZeroMQ Concepts with futures on Tokio's runtime.

Currently Supported Sockets

  • REP
  • REQ
  • PUB
  • SUB
  • PUSH
  • PULL
  • XPUB
  • XSUB
  • PAIR
  • DEALER
  • ROUTER

See the examples folder for usage examples.

Getting Started

futures = "0.1.25"
tokio = "0.1"
tokio-zmq = "0.10.1"
zmq = "0.9.1"

In your application:

use std::sync::Arc;

use futures::{Future, Stream};
use tokio_zmq::{prelude::*, Rep};

fn main() {
    let ctx = Arc::new(zmq::Context::new());
    let rep_fut = Rep::builder(ctx).bind("tcp://*:5560").build();

    let runner = rep_fut.and_then(|rep| {
        let (sink, stream) = rep.sink_stream(25).split();

        stream
            .map(|multipart| {
                // handle the Multipart
                // This example simply echos the incoming data back to the client.
                multipart
            })
            .forward(sink)
    });

    tokio::run(runner.map(|_| ()).or_else(|e| {
        println!("Error: {:?}", e);
        Ok(())
    }));
}

Running the examples

The req.rs and rep.rs examples are designed to be used together. The rep example starts a server with a REP socket, and the req example queries that server with a REQ socket.

The zpub.rs and sub.rs examples should be used togheter. zpub produces values that sub consumes.

The push.rs, pull_push.rs, and pull.rs files should be used together. push produces values, which are relayed by pull_push to pull, which consumes them and sends a stop signal to itself and to pull_push.

sync_pubsub.rs, dealer_router.rs, and load_balancing_broker are all self-contained, and spawn multiple threads.

Contributing

Feel free to open issues for anything you find an issue with. Please note that any contributed code will be licensed under the GPLv3.

License

Copyright © 2018 Riley Trautman

Tokio ZMQ is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Tokio ZMQ is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. This file is part of Tokio ZMQ.

You should have received a copy of the GNU General Public License along with Tokio ZMQ. If not, see http://www.gnu.org/licenses/.

Dependencies

~4MB
~86K SLoC