mre / futures-batch Goto Github PK

In #10 we try to move to Tokio 0.2.
Unfortunately, a lot has changed and the update requires some effort.

Mainly, the unit tests need fixing because tokio::run is no longer part of Tokio.
Instead, it's tokio::test now. See here for more info.

If someone wants to take over, that would be a great opportunity to start with async Rust and Tokio.

The Rust async ecosystem is moving fast and this crate no longer depends on Tokio.
The only dependency we have is on Stream from the futures crate.
I was wondering if we should reflect that in the project name.

The two names that I favor at the moment are futures-batch and async-batch with a slight tendency towards futures-batch. I considered stream-batch, but it doesn't have the same ring to it.

Would be interested in getting your opinions @doyoubi, @leshow, @spebern, and @wngr.

Hi,

Great lib for batching!!

Just a small problem.
The resolution of tokio-timer is too low. The smallest duration is 1 millisecond.
When batching syscall, we need to use a higher resolution timer.

futures-timer fits the needs but it requires changing the type of the Error returned.
Maybe you can consider moving from tokio-timer to futures-timer.

Hi,

Could you push the newest version to crates.io?

Thanks in advance!

futures::stream::TryStreamExt has a try_chunks method that batches Ok values and immediately propagates any Err values. I believe it would be very useful to have something like that in this library.