lemunozm/message-io

This system is a Rust networking library that provides a modular, adapter-based architecture for building networked applications. It supports multiple transport protocols, including TCP, UDP, and WebSocket, through a unified API that handles connection management, message encoding, and event processing. The library includes utilities for efficient data handling and thread management, along with examples and benchmarks to demonstrate performance and usage patterns.

5 changes.

The project launched the message-io networking library as a public crate, providing a modular API for building networked applications with support for TCP, UDP, and WebSocket transports. This release was accompanied by significant dependency updates and the addition of diverse examples, including distributed discovery, multicast, and file transfer scenarios, to demonstrate the library's capabilities.

7 changes.

The project established a pluggable network architecture with a unified Driver and Adapter trait, enabling support for TCP, UDP, and WebSocket transports. Concrete implementations for these protocols were developed alongside utility modules for encoding and threading. The period also included comprehensive integration tests, latency benchmarks, and a ping-pong example to validate the new multi-transport capabilities.

A new example demonstrating how to send and receive files over TCP using the FramedTcp transport. The example includes a receiver that listens on port 3005 and a sender that transfers files in 64KB chunks to avoid blocking the event queue, with progress reporting and support for multiple concurrent connections.

examples/file-transfer · high confidence

A new example demonstrating a distributed network architecture has been added to the examples/distributed directory. It features a discovery server that manages participant registration and unregistration, notifying other participants of network changes. Participants can register with the server, receive a list of existing members, and establish direct private communication channels with each other using Framed TCP transport.

examples/distributed · high confidence

A new example demonstrating how to use multicast for node discovery has been added to the examples directory. It shows how to connect to a multicast address, send a greeting message upon connection, and listen for messages from other nodes on the same LAN.

examples/multicast · high confidence

Introduced a new ping-pong example in the \examples/ping-pong\ directory that illustrates a client-server architecture supporting TCP, UDP, and WebSocket transports. The example includes a server that listens for connections and a client that sends periodic ping messages, with logic to handle connection-oriented versus connection-less protocols appropriately. Users can run the server and client via command-line arguments to test connectivity and message exchange across different network transports.

examples/ping-pong · high confidence

A new example application has been added to measure and compare network throughput across different transport protocols (UDP, TCP, Framed TCP, and WebSocket). The tool benchmarks both the \message-io\ library's performance and native standard library implementations by transferring 1GB of data over localhost, allowing users to evaluate protocol overhead and library efficiency.

examples/throughput · high confidence

The library is now available as a public crate, exposing a modular API for building networked applications. Users can create nodes via \node::split\ to handle connections and signals, and interact with the network through \NetworkController\ methods like \connect\ and \listen\ which support multiple transports (TCP, UDP, WebSocket) via feature flags. The API includes a synchronized event queue (\EventReceiver\) for processing network events and timers, and provides adapters for various transport protocols.

src · high confidence

The \src/adapters\ directory now provides concrete implementations for TCP, UDP, and WebSocket transports, replacing the previous placeholder or unimplemented state. The TCP adapter (\tcp.rs\, \framed\_tcp.rs\) supports non-blocking connections, source address binding, device binding (on Unix), and configurable TCP keepalive settings. The UDP adapter (\udp.rs\) adds support for broadcast messages, source address specification, and socket reuse options (\SO\_REUSEADDR\, \SO\_REUSEPORT\), with specific handling for Linux broadcast reception. The WebSocket adapter (\ws.rs\) implements frame-based communication using \tungstenite\, handling both client and server handshakes and delivering binary messages. A template adapter (\template.rs\) is also included as a reference for implementing new transports.

src/adapters · high confidence

The network subsystem has been restructured to support pluggable transport adapters via a new \Adapter\ trait and \DriverLoader\ configuration system. This change introduces a generic \Driver\ that manages resources (connections and listeners) through a unified \ActionController\ and \EventProcessor\ interface, allowing the library to support multiple transport protocols (TCP, UDP, WebSocket) independently. Users can now configure which network adapters are available by mounting them to the \DriverLoader\, and the system exposes new types like \Endpoint\, \ResourceId\, and \RemoteAddr\ to handle connection identification and address resolution across different transport types.

src/network · high confidence

Added src/util/encoding.rs, which provides varint-based message encoding and a zero-copy Decoder for handling partial data chunks, and src/util/thread.rs, which introduces a NamespacedThread wrapper that automatically names threads for better debugging and ensures threads are joined on drop.

src/util · high confidence

Added integration tests for network transport behavior; Added latency benchmark suite for network transports.

The message-io network library has been updated to version 0.19.0. This release includes significant dependency upgrades, most notably updating the tungstenite WebSocket library to version 0.26 (up from 0.20.1) and the socket2 system socket library to version 0.5.1 (up from 0.3.19). Other dependencies such as mio, strum, and crossbeam-channel have also been updated to their latest compatible versions. The Cargo.toml manifest has been expanded with comprehensive metadata, including license, description, and feature definitions for tcp, udp, and websocket support.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 68 → 74 (+6.1)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 96 → 96 (-0.4)
• Architecture 100 → 86 (-14.4)
• Maturity 52 → 57 (+5.3)
• Readiness 82 → 85 (+3.1)
• Security 72 → 100 (+27.3)
• Domain Modelling 100 → 100 (+0.0)
• Event Sourcing 100 → 100 (+0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Further orphaned files (smaller)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium CVE: [GHSA redacted] (Cargo.lock)
• Medium CVE: [GHSA redacted] (Cargo.lock)
• Medium advisory (unmaintained): RUSTSEC-2024-0375 (Cargo.lock)
• Medium advisory (unmaintained): RUSTSEC-2025-0141 (Cargo.lock)
• Medium advisory (unsound): RUSTSEC-2021-0145 (Cargo.lock)
• Medium advisory (unsound): RUSTSEC-2026-0097 (Cargo.lock)
• Medium vulnerability: RUSTSEC-2026-0204 (Cargo.lock)
• No exposed public API
• Orphaned knowledge (src/network.rs)
• Orphaned knowledge (src/node.rs)
• …and 1 more

• Ambiguous naming for similar operations. 'process_poll_event' (singular) vs 'process_poll_events_until_timeout' (plural + duration). It is unclear if the singular version processes one event and returns, or processes all available events. The plural version explicitly mentions 'until_timeout'. This suggests the singular version might be a non-blocking 'try' or single-step poll, but the naming doesn't clearly convey this distinction.
• Documentation: contradicts the code (docs/performance_benchmarks.md)
• Documentation: no installation or build instructions (README.md)
• Duplicated block (10 lines × 2) (src/adapters/tcp.rs)
• Duplicated block (13 lines × 2) (src/adapters/ws.rs)
• Duplicated block (13 lines × 2) (src/adapters/ws.rs)
• Duplicated block (13 lines × 2) (src/network/transport.rs)
• Duplicated block (14 lines × 2) (src/adapters/framed_tcp.rs)
• Duplicated block (18 lines × 2) (src/adapters/framed_tcp.rs)
• Duplicated block (6 lines × 2) (src/adapters/tcp.rs)
• Duplicated block (7 lines × 2) (src/adapters/framed_tcp.rs)
• Duplicated block (8 lines × 4) (src/adapters/ws.rs)
• Duplicated block (9 lines × 2) (src/adapters/tcp.rs)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• …and 13 more

• 3 commits — 2 feature/other, 1 fixes

• (root) — 2 commits
• src/adapters — 1 commit

• fix: Fix CI and dependabot issues (#187)
• change: Deliver every WebSocket frame that one socket read pulls in (#185)
• change: update dependencies (#193)

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

lemunozm/message-io was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.