On Sat, 2009-04-04 at 00:22 +0200, Marcus Weseloh wrote: > Hello again, > > I think I solved my problem (at least for the development server) by > monkey patching django.core.servers.basehttp.ServerHandler. Does > anybody know of any horrible side effects this might have, or can > suggest a more elegant solution?
You're not really trying to solve a valid problem here. The development server isn't intended for streaming data or anything like that. It's a very simplistic server for basic stuff. So if you're trying to do streaming, you should be using a real web server more or less immediately. During single-person testing/development with the dev server, the periodic EPIPE error is harmless and not worth doing anything about. Then you'll discover that it's not really a problem you have to worry about. Firstly, because there are a few things inside Django that prevent streaming content from working smoothly and we don't guarantee that sending an iterator to the HttpResponse's __init__ method won't consume the iterator immediately, rather than streaming it. Secondly, because that's the sort of thing that web servers are designed to handle (unexpected connection closures and the like). Django applications are things that respondsto webserver requests. It isn't something that responds directly to web browser requests, so the web server introduces a lot of shielding between your Django applications and the real, bad world of network connections. As soon as you resort to changing the development server to do anything like this, you are almost certainly increasing your level of false expectations about how the "real thing" is going to behave. It's not hard to use a real webserver, anything from Apache + modwsgi to lighttpd + fastcgi to CherryPy's single-file WSGI-compatible server. I'd really encourage you to do yourself a favour and use the real thing. Also, keep in mind that "streaming" isn't something that will happen here. That's something we'll be working on in the future, but you cannot reliably do chunked-transfer encoding of content, etc, with Django. At this point Graham Dumpleton will pipe up saying you can with modwsgi under some circumstances, by breaking the WSGI compliance (it's a fairly crippling flaw in the WSGI spec that you are forbidden to send out content that should be streamed back to the user), but it requires a lot of careful tap-dancing around some internal assumptions in Django, etc, so for all intents and purposes, no you can't in a general application. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
