We're definitely looking forward to the tokio-based version of Hyper async. In case it wasn't clear from the post, we are actually using the unreleased async version of Hyper (powered by mio/rotor) today.
You could switch to the tokio branch of hyper, my understanding is that it's pretty much stable, just waiting on the final tweaks before the impending release of tokio 0.1. We're so close...
I'm still a bit hesitant to pick up tokio and tokio-hyper so soon. We've got a lot of production miles on the current async client - on the order of billions of HTTP requests. Qualifying the new hyper code for production use will take some time. There's also still some discussion on the tokio issue tracker about problems with panicking; we'll probably wait until that category of issue is resolved before diving in.
