There's a framework called cogen and it relies on this policy. -- ionel
On Sat, Sep 18, 2010 at 12:34, Ian Bicking <i...@colorstudy.com> wrote: > On Sat, Sep 18, 2010 at 5:03 AM, Marcel Hellkamp <m...@gsites.de> wrote: > >> With WSGI it was possible to yield empty strings as long as the >> application is waiting for data and call start_response once the headers >> are final. Not perfect, but at least non-blocking. Web3 removes this >> possibility. The headers must be returned before the body iterable >> yielded its first element, empty or not. >> >> 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'm aware of what a lot of people have done with WSGI, but I'm not aware of > anyone doing an async proxy of any sort, or implementing anything in a way > where this empty string policy served any function. It's not implausible > that it *could* be used, but years of practice have shown it is not used. > > -- > Ian Bicking | http://blog.ianbicking.org > > _______________________________________________ > 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/ionel.mc%40gmail.com > >
_______________________________________________ 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
