CC @eitsupi

Thank you. I'm not familiar with tokio, so I'm not sure if this solution is a good one.
I read the following thread:
https://users.rust-lang.org/t/accessing-the-current-tokio-runtime-to-call-block-on/50090

IMO, it is best to enable users to implement the sync/async API for the driver using maybe_async or new async traits.

@zeroshade we should look at Rust APIs as part of the current effort to add async APIs

@eitsupi or @mbrobbel thoughts there?

As for this PR: I think it looks OK, but I'm not an expert on Tokio. My main question is whether the driver should instead allow you to pass your own Handle in during construction so you can provide the async runtime explicitly? Otherwise I think falling back to the ambient runtime and only creating the runtime as a last resort makes sense

Made Handle passing explicit

Thank you, this seems reasonable until async supports are implemented.