> At the end, you got the idea. > It is readable, portable, generic, etc, etc.. > "This" should be underlined in asyncio documentation. > Not the protocols, callbacks, futures, transports...
I think they're all very different objects: - callbacks, futures and coroutines are the core of asyncio; you cannot write asyncio code without directly using one of those three. - protocols and transports are low-level abstraction for communication channel; you usually don't have to use them directly. - streams are high-level abstraction; you can do without them but they really make your life easier. Also, I updated the project to make it easier to add a backdoor to a server without touching its code: $ apython --serve localhost:8888 -m some.asyncio.server --some options A python console is then accessible through: $ nc localhost 8888
