finds.dev

lemunozm/message-io

Fast and easy-to-use event-driven network library.

View on GitHub

★ 1,200RustApache-2.0updated Sep 2026

// the take

message-io is a Rust networking library that wraps raw sockets (TCP, UDP, WebSocket) behind a single event-driven API, so you write one handler and can swap transports with one line of code. It's aimed at people building game servers, chat apps, or other LAN/small-scale network tools who want socket handling without hand-rolling async I/O or picking a protocol up front.

Non-blocking I/O built on mio handles thousands of connections from a single thread, and reads/writes go straight to the OS socket buffer with zero-copy, full-duplex support. The abstraction of messages + endpoints over three different transports (TCP, UDP, WS) actually works as advertised in the README example — same handler code, different `Transport` enum value. Adding a new transport adapter is a real, documented extension point (8 trait methods, ~150 lines), not just a theoretical plugin system.

No TLS/secure WebSocket support — the README itself strikes through "secure" and links to an open issue (#102), so anything beyond a trusted LAN needs you to bolt on encryption yourself. The single-thread, non-async event loop is the whole design, which means CPU-heavy per-message work blocks everything else; the author's own docs point people with real async/await needs or P2P ambitions toward tokio or libp2p instead, which is an honest admission but also a hard ceiling. It's a one-maintainer project (lemunozm) with modest adoption (1.2k stars, a handful of listed dependents) and no wasm target, so plan for the bus factor and don't expect browser-side usage.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
1,200
Forks
84
Language
Rust
License
Apache-2.0
Last commit
17 Sep 2026

// nearby

If message-io isn't quite it.

All repos →