On Sat, Sep 18, 2010 at 5:03 AM, Marcel Hellkamp <span dir="ltr"><<a href="mailto:marc@gsites.de">marc@gsites.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
With WSGI it was possible to yield empty strings as long as the<br>
application is waiting for data and call start_response once the headers<br>
are final. Not perfect, but at least non-blocking. Web3 removes this<br>
possibility. The headers must be returned before the body iterable<br>
yielded its first element, empty or not.<br>
<br>
Removing any support for this type of asynchronism would render web3<br>
useless for all but completely synchronous and trivial applications.<br>
Even frameworks would have no way to work around this anymore.<br></blockquote><div><br>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.<br>
<br></div></div>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>