On Tue, Dec 4, 2012 at 4:15 AM, Kyle Simpson get...@gmail.com wrote:
One suggestion is to added a state to the readyState mechanism like
chunkReady, where the event fires and includes in its event object
properties the numeric index, the //@sourceURL, the separator identifier, or
otherwise
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
On Mon, Dec 3, 2012 at 6:15 PM, Kyle Simpson get...@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
On Mon, Dec 3, 2012 at 6:35 PM, Ojan Vafai o...@chromium.org wrote:
On Mon, Dec 3, 2012 at 6:15 PM, Kyle Simpson get...@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
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).
Why? What would you do in such an
On Mon, Dec 3, 2012 at 6:15 PM, Kyle Simpson get...@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
