At 09:01 AM 9/18/2010 -0700, Robert Brewer wrote:
Marcel Hellkamp wrote:
>
> Removing any support for this type of asynchronism would render web3
> useless for all but completely synchronous and trivial applications.
> Even frameworks would have no way to work around this anymore.
I've run a few businesses now on WSGI without doing what you
describe, so I don't see why blocking makes an application 'trivial'.
I believe he means: all_but(synchronous_apps + trivial_apps), not
all_but(apps(synchronous & trivial)). ;-)
(That being said, for WSGI 2 I still want to get rid of
start_response. IMO, async WSGI needs to be a different protocol.)
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
