On 1/24/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > I agree that this would be a fine feature to add. Anybody willing to > work on a patch?
I don't think I can do a patch, but I hoped to inform one. I was just reading the bits of WSGI 1.0 to understand what it says on the topic, and this note confuses me: " 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 chunk. ... (Note: applications and middleware must not apply any kind of Transfer-Encoding to their output, such as chunking or gzipping; as "hop-by-hop" operations, these encodings are the province of the actual web server/gateway. See Other HTTP Features below, for more details.) " This says that the WSGI server is responsible for chunking, not the application. The most django can do is hand off an iterable (or call write() for each iterable). It also has what I'm sure is an error in the 1st paragraph, and what I think is an error in the 2nd paragraph. "generating a Content-Length header for each chunk" has to be wrong, I think it means chuck size. In the 2nd para, it suggests gzip as a transfer-encoding, which I think is actually a content encoding. I guess I'm looking for either agreement or correction. :)
