All Projects → tokio-rs → Mio

tokio-rs / Mio

Licence: mit
Metal IO library for Rust

Programming Languages

rust
11053 projects
Makefile
30231 projects

Projects that are alternatives of or similar to Mio

Ws Machine
WS-Machine is a websocket finite state machine for client websocket connections (Go)
Stars: ✭ 110 (-97.62%)
Mutual labels:  asynchronous, non-blocking, networking
Purerpc
Asynchronous pure Python gRPC client and server implementation supporting asyncio, uvloop, curio and trio
Stars: ✭ 125 (-97.29%)
Mutual labels:  asynchronous, networking
Gnet
🚀 gnet is a high-performance, lightweight, non-blocking, event-driven networking framework written in pure Go./ gnet 是一个高性能、轻量级、非阻塞的事件驱动 Go 网络框架。
Stars: ✭ 5,736 (+24.34%)
Mutual labels:  non-blocking, networking
Tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Stars: ✭ 14,278 (+209.52%)
Mutual labels:  asynchronous, networking
Zsh Autocomplete
🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
Stars: ✭ 641 (-86.1%)
Mutual labels:  asynchronous, non-blocking
Parallel Ssh
Asynchronous parallel SSH client library.
Stars: ✭ 864 (-81.27%)
Mutual labels:  asynchronous, non-blocking
Netclient Ios
Versatile HTTP Networking in Swift
Stars: ✭ 117 (-97.46%)
Mutual labels:  asynchronous, networking
RxIo
Asynchronous non-blocking File Reader and Writer library for Java
Stars: ✭ 20 (-99.57%)
Mutual labels:  asynchronous, non-blocking
Future
High-performance Future implementation for the JVM
Stars: ✭ 223 (-95.17%)
Mutual labels:  asynchronous, non-blocking
Simplenet
An easy-to-use, event-driven, asynchronous network application framework compiled with Java 11.
Stars: ✭ 164 (-96.44%)
Mutual labels:  asynchronous, networking
Cmd
Non-blocking external commands in Go with and streaming output and concurrent-safe access
Stars: ✭ 477 (-89.66%)
Mutual labels:  asynchronous, non-blocking
Message Io
Event-driven message library for building network applications easy and fast.
Stars: ✭ 321 (-93.04%)
Mutual labels:  asynchronous, non-blocking
Tls Channel
A Java library that implements a ByteChannel interface over SSLEngine, enabling easy-to-use (socket-like) TLS for Java applications.
Stars: ✭ 113 (-97.55%)
Mutual labels:  non-blocking, networking
Base64 Async
Non-blocking chunked Base64 encoding
Stars: ✭ 98 (-97.88%)
Mutual labels:  asynchronous, non-blocking
Joynet
high performance network (tcp socket) library for lua, based on https://github.com/IronsDu/brynet and lua coroutine.
Stars: ✭ 101 (-97.81%)
Mutual labels:  non-blocking, networking
Swift Nio
Event-driven network application framework for high performance protocol servers & clients, non-blocking.
Stars: ✭ 6,777 (+46.91%)
Mutual labels:  non-blocking, networking
Zap
An asynchronous runtime with a focus on performance and resource efficiency.
Stars: ✭ 162 (-96.49%)
Mutual labels:  asynchronous, networking
Lightning
A Swift Multiplatform Single-threaded Non-blocking Web and Networking Framework
Stars: ✭ 312 (-93.24%)
Mutual labels:  asynchronous, non-blocking
Libuv
Cross-platform asynchronous I/O
Stars: ✭ 18,615 (+303.53%)
Mutual labels:  asynchronous, networking
Bocadillo
(UNMAINTAINED) Fast, scalable and real-time capable web APIs for everyone
Stars: ✭ 401 (-91.31%)
Mutual labels:  asynchronous

Mio – Metal IO

Mio is a fast, low-level I/O library for Rust focusing on non-blocking APIs and event notification for building high performance I/O apps with as little overhead as possible over the OS abstractions.

Crates.io MIT licensed Build Status Build Status

API documentation

This is a low level library, if you are looking for something easier to get started with, see Tokio.

Usage

To use mio, first add this to your Cargo.toml:

[dependencies]
mio = "0.8"

Next we can start using Mio. The following is quick introduction using TcpListener and TcpStream. Note that features = ["os-poll", "net"] must be specified for this example.

use std::error::Error;

use mio::net::{TcpListener, TcpStream};
use mio::{Events, Interest, Poll, Token};

// Some tokens to allow us to identify which event is for which socket.
const SERVER: Token = Token(0);
const CLIENT: Token = Token(1);

fn main() -> Result<(), Box<dyn Error>> {
    // Create a poll instance.
    let mut poll = Poll::new()?;
    // Create storage for events.
    let mut events = Events::with_capacity(128);

    // Setup the server socket.
    let addr = "127.0.0.1:13265".parse()?;
    let mut server = TcpListener::bind(addr)?;
    // Start listening for incoming connections.
    poll.registry()
        .register(&mut server, SERVER, Interest::READABLE)?;

    // Setup the client socket.
    let mut client = TcpStream::connect(addr)?;
    // Register the socket.
    poll.registry()
        .register(&mut client, CLIENT, Interest::READABLE | Interest::WRITABLE)?;

    // Start an event loop.
    loop {
        // Poll Mio for events, blocking until we get an event.
        poll.poll(&mut events, None)?;

        // Process each event.
        for event in events.iter() {
            // We can use the token we previously provided to `register` to
            // determine for which socket the event is.
            match event.token() {
                SERVER => {
                    // If this is an event for the server, it means a connection
                    // is ready to be accepted.
                    //
                    // Accept the connection and drop it immediately. This will
                    // close the socket and notify the client of the EOF.
                    let connection = server.accept();
                    drop(connection);
                }
                CLIENT => {
                    if event.is_writable() {
                        // We can (likely) write to the socket without blocking.
                    }

                    if event.is_readable() {
                        // We can (likely) read from the socket without blocking.
                    }

                    // Since the server just shuts down the connection, let's
                    // just exit from our event loop.
                    return Ok(());
                }
                // We don't expect any events with tokens other than those we provided.
                _ => unreachable!(),
            }
        }
    }
}

Features

  • Non-blocking TCP, UDP
  • I/O event queue backed by epoll, kqueue, and IOCP
  • Zero allocations at runtime
  • Platform specific extensions

Non-goals

The following are specifically omitted from Mio and are left to the user or higher-level libraries.

  • File operations
  • Thread pools / multi-threaded event loop
  • Timers

Platforms

Currently supported platforms:

  • Android (API level 21)
  • DragonFly BSD
  • FreeBSD
  • Linux
  • NetBSD
  • OpenBSD
  • Windows
  • iOS
  • macOS
  • Wine (version 6.11+, see issue #1444)

There are potentially others. If you find that Mio works on another platform, submit a PR to update the list!

Mio can handle interfacing with each of the event systems of the aforementioned platforms. The details of their implementation are further discussed in the Poll type of the API documentation (see above).

The Windows implementation for polling sockets is using the wepoll strategy. This uses the Windows AFD system to access socket readiness events.

Unsupported

Community

A group of Mio users hang out on Discord, this can be a good place to go for questions.

Contributing

Interested in getting involved? We would love to help you! For simple bug fixes, just submit a PR with the fix and we can discuss the fix directly in the PR. If the fix is more complex, start with an issue.

If you want to propose an API change, create an issue to start a discussion with the community. Also, feel free to talk with us in Discord.

Finally, be kind. We support the Rust Code of Conduct.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].