Sure. You probably would want to escape from wsgi for the couple of urls in your application that really need to be async, while writing the traditional parts traditionally. You can also do pretty well with wsgi and greenlets (which iirc is how mongrel2 is written internally - asynchronous code written in a synchronous style).
On Jun 24, 2012, at 9:39 PM, James Dennis <[email protected]> wrote: > It's not asynchronous. WSGI cannot properly do asynchronous anything. It is a > straight-line of requests that must be handled in the same order they're > submitted. Thus, people have to write special code for long-polling or > websockets rather than work through existing systems. > > > On Sun, Jun 24, 2012 at 9:28 PM, Daniel Holth <[email protected]> wrote: > Uwsgi is useful because it is provides a complete platform for writing > clustered web applications, including process management, spooling, and too > many other things to mention. Great to see it working better with the > asynchronous zeromq power of mongrel2. > > Daniel Holth >
