W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2012

Re: [whatwg] Loading and executing script as quickly as possible using multipart/mixed

From: Adam Barth <w3c@adambarth.com>
Date: Mon, 3 Dec 2012 23:14:39 -0800
Message-ID: <CAJE5ia8yvxGFjWQfjNwbVXq1jV76kZT9ksTaDzep3CGtjzmOEQ@mail.gmail.com>
To: Kyle Simpson <getify@gmail.com>
Cc: whatwg <whatwg@lists.whatwg.org>
On Mon, Dec 3, 2012 at 6:15 PM, Kyle Simpson <getify@gmail.com> wrote:
> Adam-
>> To load and execute a script as quickly as possible, the author would
>> use the following markup:
>> <script async src="path/to/script.js"></script>
>> The HTTP server would then break script.js into chunks that are safe
>> to execute sequentially and provide each chunk as a separate MIME part
>> in a multipart/mixed response.
> I like the spirit of this idea, but one concern I have is about the script load and readystate events. It seems that authors will want to know when each chunk has finished executing (in the same way they want to know that scripts themselves finish).

Sure, you could imagine firing progress events or other sorts of
events before or after each chunk executes.

Received on Tuesday, 4 December 2012 07:44:45 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:50 UTC