Sebastian Thiel 5adde38a65 Allocation in get_mut() always uses 8 * 1024 bytes
The previous implementation would always use the capacity
of the previous buffer, which would effectively prevent it
from ever shrinking.

This also means that protocol with greater variance in
possible frame sizes would likely be heavily over-allocating.
If these implementations use zero-copy, this would imply
that even small frames kept alive by the client would use
large amounts of memory.

The change is motivated by the implementation of the
cassandra-protocol, which allows frames of up to 256MB
in size, which solely depend on the kind of query.
2017-02-11 09:01:07 +01:00
2016-11-19 10:02:12 -08:00
2017-01-24 20:52:48 -08:00
2016-11-19 09:40:33 -08:00
2016-08-26 14:45:55 -07:00
2017-01-24 16:39:01 -08:00
2016-08-26 14:56:21 -07:00
2016-08-26 14:56:21 -07:00
2017-01-11 09:14:50 -08:00

tokio-core

Core I/O and event loop abstraction for asynchronous I/O in Rust built on futures and mio.

Build Status Build status

Documentation

Tutorial

Usage

First, add this to your Cargo.toml:

[dependencies]
tokio-core = "0.1"

Next, add this to your crate:

extern crate tokio_core;

You can find extensive documentation and examples about how to use this crate online at https://tokio.rs as well as the examples folder in this repository. The API documentation is also a great place to get started for the nitty-gritty.

License

tokio-core is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.

See LICENSE-APACHE, and LICENSE-MIT for details.

Description
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Readme MIT 76 MiB
Languages
Rust 100%