support for futures::io::AsyncRead/Write

[Licenser]

It seems that hyper uses tokio's AsyncRead / Write trait not the futures-0.3 one which makes it hard to mix with other libraries - would it be possible to implement both of the traits for hyper?

For context: I'm trying to upgrade a http connection to a websocket connection using async-tungstenite

[davidbarsky]

I don't think this will happen happen for a bit. For additional details, see: tokio-rs/tokio#1744.

If I recall correctly, there is a crate that provides compatibility between Tokio's AsyncRead/Write and Futures' AsyncRead/Write, but I can't seem to find it right now.

[Licenser]

No worries I gave up and put the web server on its own port, in fortunate that I can do that right now. There are more issues like different runtimes that make it impossible even when working around this. I’ll just go back to my cave for a few month and hope the Async ecosystem has stabilized in n something

[seanmonstar]

Yea, as mentioned, the reason we're using Tokio's traits is because we'd like to consider alternative designs to the one proposed in futures-io.

[jinq0123]

hyper-futures
Compatibility layer for futures to use AsyncRead and AsyncWrite traits with hyper

If I recall correctly, there is a crate that provides compatibility between Tokio's AsyncRead/Write and Futures' AsyncRead/Write, but I can't seem to find it right now.

async-compat
v0.2.4
Compatibility adapter between tokio and futures

[jinq0123]

Trait tokio_util::compat::FuturesAsyncReadCompatExt
Extension trait that allows converting a type implementing futures_io::AsyncRead to implement tokio::io::AsyncRead.

[jinq0123]

Struct smol_hyper::rt::FuturesIo
This type implements hyper I/O traits for [futures-io] implementors.