PEP 333 indicates chunked encoding is ok in WSGI apps:
"And, if the server and client both support HTTP/1.1 "chunked
encoding" [3], then the server may use chunked encoding to send a
chunk for each write() call or string yielded by the iterable, thus
generating a Content-Length header for each
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
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
On Tue, 2008-07-08 at 13:31 -0700, 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.
Not really (in a reliable way).
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
5 matches
Mail list logo
