deft
deft copied to clipboard
Chunked transfer-encoding
If a server wants to start sending a response before knowing its total length (like with long script output), it might use the simple chunked transfer-encoding, which breaks the complete response into smaller chunks and sends them in series. You can identify such a response because it contains the "Transfer-Encoding: chunked" header.
See: http://www.jmarshall.com/easy/http/#http1.1s3
Question is if we really need this?
I dont know. Lets investigate it a little bit more before deciding if this should make it into 0.1.0 or not.
after looking at Ryan Dahl's (author of node.js) introduction to node.js (from node.js camp 2010, http://camp.nodejs.org/videos/session-01_introduction_to_node-ryan_dahl.html) I think we should support this.
http://weblog.rubyonrails.org/2011/4/18/why-http-streaming