Yeah all the warts in WSGI are basically because of streaming. They should have been 2 APIs. Nobody likes start_response, and I think that was because of stre

Yeah all the warts in WSGI are basically because of streaming. They should have been 2 APIs. Nobody likes start_response, and I think that was because of streaming. Although I suppose you could still return a 3-tuple (status, headers, body) and still have the body be iterable, so maybe I'm wrong.