HTTP Streaming. Transfer-Encoding: chunked. Web browsers. Etc.
Rails 3.1 is going to support HTTP streaming, aka chunked responses, this post explains what's all about. What Is HTTP Streaming? Ordinary dynamic HTTP responses need a Content-Length header. Their timeline look like this: HTTP request -> dynamic content generation -> HTTP response Those are three serial steps because normally you need to generate the content in order to be able to know its size, and thus fill the Content-Length header of the response. HTTP provides an alternative to this schema to be able to flush data as it is produced, known as chunked transfer encoding . That's what we are referring to as streaming in recent commits. Streamed responses have no Content-Length header. Rather, they have a Transfer-Encoding header with a value of "chunked", and a body consisting of a series of chunks you write to the socket preceded by their individual sizes. Modulus detai...