Oboe.js: reacting to Ajax/Rest quicker by not waiting for it to finish

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by joombar on Friday October 18, 2013 @10:19AM (#6571479)

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.

[ Parent | on HN ]

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by tambourine_man on Friday October 18, 2013 @11:09AM (#6571783)

From 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.

[ Parent | on HN ]

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by mbrock on Friday October 18, 2013 @11:40AM (#6571962)

Gzip 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.

[ Parent | on HN ]