To me, asyncio already provides a de-facto standard API for
asynchronous backends and Tornado/Twisted provide a high level API on
top of it. I have to say, I don't precisely grasp what WSGI actually
wishes to bring to the table.
I guess if we're really talking about this, the lowest common
denomin
Fascinating and exciting.
Up until now, my go-to tactic for contain WSGI inside async has been
to use the WSGI container in twisted.web (this is how hendrix works:
https://github.com/hangarunderground/hendrix).
However, if we're talking about an actual flag in WSGI (like
wsgi.async_input), this i
