2014-03-26 12:41 GMT+01:00 Victor Stinner <[email protected]>:
> I would like to know which WSGI implementations are compatible with > Tulip/asyncio (and maybe also Trollius!). > As far as I understand, WSGI as defined by PEP 3333 is incompatible with asyncio. The WSGI callable would have to become a coroutine for asyncio to do something useful and the specification doesn't allow that. At this point, from what I've seen, authors of web applications tend to separate their sync and async services because the performance characteristics are widely different. As far as I know and judging from past attempts, a PEP adding async support to WSGI would be met with fierce resistance. (I had started writing one but I gave up after reading discussions on the topic.) If a WSGI implementation is not designed for asyncio, is it still > possible to run asyncio tasks in an handler? > Most likely yes, by running the main server loop and the asyncio event loop in different threads. -- Aymeric.
