zenoh
MIO
zenoh | MIO | |
---|---|---|
13 | 21 | |
1,259 | 6,087 | |
3.9% | 1.2% | |
9.6 | 8.4 | |
6 days ago | 7 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zenoh
- Zenoh: Zero Overhead Network Protocol
- Eclipse Zenoh 0.10.0 is out
-
Can I use several async runtimes in the same project?
I'm very new to Rust and currently I'm trying to make sense of async programming in Rust. In my project I'm trying to create an http + websocket server (I picked Actix) that communicates to a CPP program over DDS and sends the result of this communication to some frontend over http/ws. I use Zenoh for leveraging communication between my Rust app and CPP, and it has it's own crate for creating a zenoh client in Rust. In the documentation they use async-std macros for the main function and Actix uses Tokio under the hood, as far as I understand. Is this gonna be a problem? Can I have several async runtimes in my project?
- Need recommendations for technologies, frameworks etc. for an IoT device project in Rust
-
Anouncing `stabby` 1.0!
Zenoh's plugin system was one of the main motivators for building stabby. However, Zenoh needs me on other fronts at the moment, so stabby will have to go to the back burner for a bit. This doesn't mean stabby will become unsupported: if you want to use it, and are having a hard time, feel free to DM me to get some support. In fact, what stabby needs most right now is feedback on what types you'd like to see supported, so go for it!
- Zenoh – Zero Overhead Network Protocol
-
Zenoh Performances
Hello u/ComeGateMeBro, in zenoh we have zero-copy support, this is an example that shows how to use it: https://github.com/eclipse-zenoh/zenoh/blob/master/examples/examples/z_pub_shm.rs
-
Rust MPI -- Will there ever be a fully oxidized implementation?
The next step would be to use the zenoh crate, which will simplify a lot of things.
-
This week in Rust 479 - Eclipse Zenoh release
The new Eclipse Zenoh 0.7.0 release, codename Charmander, brings to the table many features requested by the community on the Zenoh’s Discord server.
-
Eclipse Zenoh: 0.7.0 release
The Rust code is hosted here: https://github.com/eclipse-zenoh/zenoh While the Rust docs is hosted here: https://docs.rs/zenoh/0.7.0-rc/zenoh/ It's available on crates.io: https://crates.io/crates/zenoh
MIO
-
What's the canonical way of doing it in rust?
Was playing around with mio (https://github.com/tokio-rs/mio) (not that mio itself is very important here!) and was trying to implement a simple something that I've done in java before: a Reactor that you can register ReactorClients with that will get callback whenever there are events on the corresponding socket etc.
-
RFC: A non-blocking networking library for Rust
How does it compare to mio?
-
How does the Rust mio crate implement deregistering connections?
TcpStream gets its wake behavior by delegating to the fd wakers. The Unix wakers have a few implementations, for different platforms. On Linux and Android, epoll is used.
-
Looking for Tokio's event loop source code
The real implementation details of the I/O event queue is done in mio as u/hniksic pointed out, but that's more comparable with libuv which is certainly a huge part of the Node runtime. mio and libuv have a lot of similarities (at least they used to).
-
Python multi-level break and continue
My example was "twice by one developer", not "twice across all indexed repos."
A spot check shows that quite a few in your link are used specifically to ensure correct handling of Rust multi-level breaks work syntax, like https://github.com/rust-lang/rust-analyzer/blob/master/crate... , https://github.com/rust-lang/rustfmt/blob/master/tests/sourc... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... and likely more.
Another is a translation of BASIC code to Rust, using break as a form of goto. https://github.com/coding-horror/basic-computer-games/blob/e...
The example at https://github.com/tokio-rs/mio/blob/master/tests/tcp.rs is a nice one
// Wait for our TCP stream to connect
-
Crates to help with event-loop type pattern?
In my program, I have about 6 different components that follow the pattern below. Basically, the components run a thread while polling on crossbeam channels, file descriptors or sockets. For polling, I am using Mio (https://github.com/tokio-rs/mio).
-
Ask HN: Has any Rust developer moved to embedded device programming?
On the code side it's pretty much the same as C++. You have a module that defines an interface and per-platform implementations that are included depending on a "configuration conditional checks" #[cfg(target_os = "linux")] macro.
https://github.com/tokio-rs/mio/blob/c6b5f13adf67483d927b176...
- Mio - Metal io library for rust
-
`wasm32-wasi` support added to Tokio
Made possible by Wasi support for Mio https://github.com/tokio-rs/mio/pull/1576
-
What is the point of async and await?
Indeed! In practice it's done through the polling operation: instead of a separate poll for op1 and op2, the program essentially tells the OS "wake me when either op1 or op2 is ready" (through the epoll syscall on Linux). The mio crate implements this, and the example on the readme is basically the same loop, but written with this polling strategy in mind.
What are some alternatives?
zmq.rs - A native implementation of ØMQ in Rust
tokio
areg-sdk - AREG is an asynchronous Object RPC framework to simplify multitasking programming by blurring borders between processes and treating remote objects as if they coexist in the same thread.
rust-zmq - Rust zeromq bindings.
sniffnet - Comfortably monitor your Internet traffic 🕵️♂️
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
libpnet - Cross-platform, low level networking using the Rust programming language.
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
actix - Actor framework for Rust.
canary - Distributed systems library for making communications through the network easier, while keeping minimalism and flexibility.
message-io - Fast and easy-to-use event-driven network library.