Thanks for the information. I was hoping to use Django for all of the web application I'm building (which requires a continuous stream of data to the client rather than poling) though it appears I'll have to build the streaming portion outside of Django, or perhaps modify the server behavior to handle the stream URL at a low level in the server. I'm not really too excited about having to essentially build another web server and run it on another port so I'm looking at modifying (subclassing actually) basehttp.ServerHandler to expose the output stream. This seems to work for this low level requirement, though obviously using the stream directly is dangerous within the higher level components.
thanks, Dave On Jul 8, 7:47 pm, Joshua Jonah <[EMAIL PROTECTED]> wrote: > Not that i know of, but you'd be surprised how easy it is to write a > socket server in Python: > > http://www.amk.ca/python/howto/sockets/ > > Brogli wrote: > > Hi, > > Is there an easy way to get a handle to the output file stream in a > > Django application? Instead of building an entire response in memory > > then sending it out, I'd like to send the response in pieces. > > > thanks, > > Dave --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
