Hi Tai, On Mon, Aug 20, 2012 at 08:39:07AM -0700, Tai Lee wrote: > I'd like to re-visit the discussion surrounding #7581 [1], a ticket about > streaming responses that is getting quite long in the tooth now, which Jacob > finally "accepted" 11 months ago (after a long time as DDN) and said that it > is > clear we have to do *something*, but *what* remains to be seen.
Since the last time this came up I've wondered if the simplest solution might be to make it easier to integrate raw WSGI apps into a site. I still am not 100% sure it's the right approach but I thought it was worth mentioning. The argument for this is that the use cases for streaming responses are usually corner cases that are well outside of Django's sweet spot. They go against the grain of the Django's flexible request/response handling (middleware in particular). But they would be trivial to handle in a raw WSGI app. If Django made it easy to hand off requests to a WSGI app (i.e. mount the app somewhere in the URLconf and perhaps expose authentication and/or other session data) the framework could get out of the way and let the WSGI app have more direct control over response handling. I think there are probably other scenarios where easy WSGI integration would be beneficial, too. For what it's worth... Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.rapidrollout.com
signature.asc
Description: Digital signature
