tokio+mio is "async io + event loop". I think tokio-fiber tries to build coroutines on top of it. This is (or, will be) the "officially endorsed" async model f

tokio+mio is "async io + event loop". I think tokio-fiber tries to build coroutines on top of it. This is (or, will be) the "officially endorsed" async model for the server side. All the libraries you'll be using *hyper, etc) are going to be integrated with it. It's not yet finished, but when it is it will be. In the future if we get async/await that would be an even more ergonomic thing that can be used with futures (and hence, tokio), but most of the machinery is already planned for tokio itself.