On Sun, Jun 5, 2011 at 11:51 PM, Eric Covener <covener@xxxxxxxxx> wrote: > On Sun, Jun 5, 2011 at 5:40 PM, Xavier Noria <fxn@xxxxxxxxxxx> wrote: >> On Sun, Jun 5, 2011 at 11:36 PM, Eric Covener <covener@xxxxxxxxx> wrote: >> >>>> If Passenger has to dechunk, and we want a chunked compressed >>>> response, and Apache is the one responsible for doing that, how should >>>> we signal Apache that we want compression and streaming for that >>>> particular response. >>> >>> This is the main path of just configuring mod_deflate. ÂNothing else >>> required. ÂOnly passenger cares how passenger decided what the content >>> of the response was, to everyone else it's just buckets of data. >>> >>> "Streaming" just means the module that generates the content of the >>> response routinely hands some data off to Apache to send off to the >>> client rather then e.g. waiting until it's 100% done. ÂIt's also not >>> something you need to configure. >> >> But there has to be something else, because in streaming I want a >> chunked response that should start sending chunks to the client as >> soon as possible. >> >> If the back server sent just 200 bytes in the first chunk, I want >> those 200 bytes compressed and forwarded to the client exactly now. In >> particular there's no Content-Length computed. > > Does passenger pass the first 200 bytes to Apache? > > Does it follow them with a "flush bucket"? > > Does the protocol passenger uses on the backend allow your app to tell > it when to flush? > > Does the result change when you turn on mod_deflate (the preceding > questions are probably best asked on a passenger list, with this final > questions answer in-hand) Excellent! I'll ask that to the Passenger guys. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx