- From: Yoav Weiss <yoav@yoav.ws>
- Date: Thu, 28 Aug 2014 23:51:34 +0200
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: whatwg <whatwg@lists.whatwg.org>
On Thu, Aug 28, 2014 at 11:34 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 8/28/14, 5:31 PM, Yoav Weiss wrote: > >> Wouldn't that be something that is best handled as part of HTTP? e.g. >> sending a flag with the request indicating whether the resource can be >> progressively decoded or not? >> > > Can we define "progressively decoded"? > > Firefox is moving to a setup where we will progressively parse scripts, > and possibly progressively bytecode-compile, and possibly progressively > native-code-compile in the cases when we do AOT compilation, but obviously > not progressively execute. Maybe the flag should indicate a "please send this progressively" hint to the server. Then the browser is free to send whatever hint to the server that gives it best performance. If receiving multiple resources progressively provides better performance then having the server sending them one after the other, then the hint should be sent.
Received on Thursday, 28 August 2014 21:51:59 UTC