8 releases (breaking)
0.7.0 | Mar 21, 2021 |
---|---|
0.6.0 | Mar 20, 2021 |
0.5.0 | Nov 27, 2020 |
0.4.0 | Nov 27, 2020 |
0.1.0 | Nov 7, 2020 |
#1372 in Network programming
43KB
950 lines
Note that this library is in the very early stages of development! Anything and everything may change!
zedmq
A Lightweight, Safe, pure-Rust ØMQ/ZMTP library implementation
Index
Brief
Zedmq is a native implementation of ØMQ in Rust focusing on:
- being as lightweight as possible.
- being completely safe.
- providing a simple, blocking, obvious API.
This library is lazy and blocking, no work is done unless a call to a
recv
or send
is made. There is no "background" thread or task accepting
new connections or performing reconnections on the users behalf
consequently there is no shared state or synchronization being performed.
Caveats
Currently this library only supports connecting sockets over TCP, no binding behaviour is available.
Also only a few socket types have been implemented: REQ, REP, PULL, PUSH, SUB, and PUB.
Frame<'_>
and FrameBuf
This library also exposes the underlying ZMQ concept of a frame.
Additionally a distinction is made with the Frame
and FrameBuf
types
for optimization purposes.
Conceptually a Frame<'_>
is equivelent to &'_ [u8]
or &'_ str
and
the FrameBuf
equivelent is Vec<u8>
or String
. This distinction is
made in an attempt to make "zero copy" or "zero heap" practice easier.
REQ
and REP
The design of REQ
and REP
sockets are symetrical and rendered safe
through the use of the type system.
A Req
socket only has .connect
and .send
methods, .send
of which
consumes the socket and returns a ReqPending
socket which only has a .recv
method which in turn returns a multipart message and Req
socket tuple.
Same goes for the Rep
socket except that Rep
has .recv
and
RepPending
has .send
.
This done on purpose, its value is that there are no accidental footguns
involved with accidentially .send
ing when you are only allowed to .recv
or vice versa. Plus it removes the cost of runtime checking.
Examples
use zedmq::prelude::*;
fn main() -> std::io::Result<()> {
let mut socket: Pull = zedmq::connect("tcp", "127.0.0.1:5678")?;
while let Ok(message) = socket.recv() {
dbg!(message);
}
Ok(())
}
Comparison with other libraries
Library | async? | ZMTP-type? |
---|---|---|
zedmq | no (blocking) | native |
zmq.rs | yes (tokio,async-std) | native |
rust-zmq | yes (nonblocking sockets) | no (wraps libzmq) |
rust-zmq is a Rusty wrapper around libzmq which is written in C and performs its own threading and event management underneath, if you want to use libzmq from Rust consider this.
zmq.rs is an effort by the ZeroMQ community to make a pure Rust ZMQ implementation, it is currently experimental and async only with support for both tokio and async-std runtimes.
zedmq, yours truly, is my attempt at a ZMQ library in pure Rust but I didn't just want to go and use the same "async" approach as zmq.rs because they already do it just fine. So instead I took inspiration from ureq and made a "simple" ZMQ library in Rust with an obvious, safe, and blocking API.
zedmq compared to the other two libraries is the most lightweight (but note its currently the most underdeveloped.) it does not intend to compete with the other two libraries mentioned the same way ureq does not intend to compete with reqwest or hyper it is an alternative solution that wants to give Rust users a pleasant usage experience.
It does not (unlike other pure implementions of ZMQ) blindly copy the libzmq API. Instead you get a Rust-y library that is cheap, safe, and (hopefully) fun to use.
License: MIT