On Fri, Apr 2, 2010 at 05:34, Martin Aspeli <optilude+lists@gmail.com> wrote:
Eeek. Any idea how that happened? Presumably, thread control in a WSGI scenario would be up to the WSGI web server, not Zope 2.
Which may be the case here to, ie, it was the Twisted integration that was single threaded. I don't remember the details any more actually. I also don't remember how the thread support with ZServer works.
I implemented IStreamIterator support in repoze.zope2; it's actually pretty easy, since a stream iterator is an iterable, just like a WSGI response. I think you can just chuck it back. The only thing to watch out for is that you don't accidentally unwind it anywhere.
Sounds good. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64