[Twisted-web] Re: [Web-SIG] WSGI woes

[Peter Hunt]

Alan, that design looks okay. A bit complex, but it works well once
you sit down to look at it.

It would be nice if applications that didn't need a separate thread
didn't use one up, so performance-oriented programmers (like the
Twisted/Nevow guys) won't be able to have that excuse. Perhaps
start_response() could have a "threaded" boolean optional argument
that defaults to true which decides whether or not the iterable will
be called in a separate thread. This, of course, requires that the
application callable itself doesn't have any blocking code.

Does this requirement overcomplicate things?