message-io
| message-io | netty-rs | |
|---|---|---|
| 15 | 4 | |
| 1,036 | - | |
| - | - | |
| 5.8 | - | |
| 3 months ago | - | |
| Rust | ||
| Apache License 2.0 | - |
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.
message-io
-
Looking for help deciding which library to use for networking
message-io: a networking library meant to be very simple, built on mio.
-
Crate to build network packets over UDP
Another one I know about, but have not looked into yet, is message-io.
- Is there a proper websockets server framework in Rust?
-
Netty-rs - small rust library to easily write server/client networking protocols at application level
I'm working in a transport network library that possible fits as a building block for yours and solves the problem of using different underlying transports: message-io
-
Announcing message-io 0.12 - an event-driven message library to build network applications easy and fast. Now with zero-copy write/read messages. Performance close to using native OS socket with all the facilities the library offers.
Here is benchmarks
-
Someone built a chat backend with Rust for a production website?
I think https://github.com/lemunozm/message-io can be a good candidate.
-
message-io: an event-driven message library to build network applications easy and fast. Now with WebSocket support
The idea behind message-io is not to populate a current transport with a lot of options/profiles/modifications... this obfuscates the default way of working with it. Instead, if you want to build some behaviour on top of it, it is as easy as making an adapter! Following this pattern, you can split the way of using the library from the behaviour of the transport, keeping the things simple.
-
termchat: Terminal chat application on LAN with file transfer and ASCII webcam video streaming support. Built on top of tui-rs and message-io crates
The initial purpose was to show the capabilities of https://github.com/lemunozm/message-io Nevertheless, Termchat is growing and needs to polish some of its features. At this point it is not for real-world use but I hope to reach this target.
netty-rs
- Show HN: Netty-rs – Rust library to easily write server/client network protocols
- Create network protocol easily with Netty-rs
- Netty-rs - small rust library to easily write server/client networking protocols at application level
- Show HN: I wrote small rust crate to help build stateful app protocols for P2P
What are some alternatives?
MIO - Metal I/O library for Rust.
Netty - Netty project - an event-driven asynchronous network application framework
tungstenite-rs - Lightweight stream-based WebSocket implementation for Rust.
laminar - A simple semi-reliable UDP protocol for multiplayer games
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
criterion.rs - Statistics-driven benchmarking library for Rust
ws-rs - Lightweight, event-driven WebSockets for Rust.
rust-sloth - A 3D software rasterizer... for the terminal!
sniffnet - Comfortably monitor your Internet traffic 🕵️♂️
quinn - Async-friendly QUIC implementation in Rust
lam - :rocket: a lightweight, universal actor-model vm for writing scalable and reliable applications that run natively and on WebAssembly