Here's a nice breakdown <http://www.jmarshall.com/easy/http/#http1.1c2> of what clients expect when a response uses Chunked Transfer-Encoding.
- Mike On Wed, Apr 14, 2010 at 5:19 PM, Clifford Heath <[email protected]>wrote: > On 14/04/2010, at 5:12 PM, Nathan de Vries wrote: > >> On 14/04/2010, at 5:02 PM, Clifford Heath wrote: >> >>> Doesn't the Rack API make it impossible? >>> >> Rack can be handed an input stream of indeterminate length via rack.input, >> so in theory the API does support it. That being said, my blog entry was >> about Passenger's support for accepting incoming requests with a chunked >> transfer encoding, so I'm not sure what would be involved in chunking >> outgoing requests for the purposes of speeding up page loads. >> > > Hmm, ok. Anyhow, it sounds promising; does this mean that Passenger apps > can receive > partial data chunks, such as you might use in a COMET situation? I guess > there's no > real point unless Rack knows when to send partial output, but still... > > Clifford Heath. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
