W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: Out-of-order Frames

From: Zhong Yu <zhong.j.yu@gmail.com>
Date: Sat, 22 Jun 2013 20:45:51 -0500
Message-ID: <CACuKZqF-FEpLCAMYPNeYtY=16brwhStu=nBbWVEZjbD0+5JT-A@mail.gmail.com>
To: Sam Pullara <spullara@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
this reminds me another request for out-of-order delivery of an http entity


(it would be funny though to implement out-of-order frams on top of
TCP which already deals with out-of-order segments)

Zhong Yu

On Sat, Jun 22, 2013 at 2:34 PM, Sam Pullara <spullara@gmail.com> wrote:
> Commonly in dynamically generated websites there are sections of content that are static and parts that are calculated on a per request basis. The current best practice for accelerating the delivery of a page like this involves leaving identifiable DOM elements where the dynamic content would appear, flushing the entire static page, and then flushing JavaScript script nodes as calculations complete (e.g. Facebook's BigPipe and deferred rendering in mustache.java). This practice only works for HTML pages (with JavaScript enabled) and offers no acceleration for other types of content delivered over HTTP.
> One possible solution to this problem would be to allow for out-of-order frames where the static frames are sent as quickly as the connection allows and dynamically generated frames are then sent later as they become available on the server. We would likely not want to enable this in general and would likely need to negotiate this behavior between client and server. Looking at the spec, frames might not be the right place but something on top of frames because of the size limitations.
> Has something like this been discussed before? Would this be the right mechanism or are there better ways to do it?
> Thanks,
> Sam
Received on Sunday, 23 June 2013 01:46:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:11 UTC