30 ms·
I'll have to test to be sure you still get streaming. It depends how the browsers handle xhr2 events with regard to gzip'd http. I /think/ it'll be fine but I n
by joombar 13y ago
I'll have to test to be sure you still get streaming. It depends how the browsers handle xhr2 events with regard to gzip'd http. I /think/ it'll be fine but I need to check to be sure. Eg, with gzip on you still get progressive html rendering.
- tambourine_man 13y agoFrom what I remember, Apache will send you a single chunk if you have it on, for example: <? echo 'Hey<br>'; flush(); ob_flush(); sleep(20); echo 'Bye'; ?> Will send you "Hey<br>Bye" after 20sec instead of what you would expect (which does work with gzip off). Besides, even if you manage to stream it, I imagine inflating partially received content is not trivial for the browser.
- mbrock 13y agoGzip is a streaming format -- it's designed as a compressed format for communication streams. Browsers have no trouble with this. The Apache behavior you describe is probably related to buffering settings, which I think can be configured.