>> Regarding the "stream style", I can share some of my >> experience: >> >> For code below, other than some limited portion >> and awaits, can you see any line specific to asyncio? No? >> >> Well that's the point. With some little search replace, >> and tweaks it can easily be transformed into >> equivalent multithreaded version. Even to a C++ version.
> 3. implementing a protocol completely using asyncio coroutines and > streams makes the implementation itself more readable, so it can be a goal > in itself. 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...
