W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2014

Re: [whatwg] Preloading and deferred loading of scripts and other resources

From: Yoav Weiss <yoav@yoav.ws>
Date: Tue, 2 Sep 2014 10:34:04 +0200
Message-ID: <CACj=BEhD3kD4ed2up4K_24=2t14CEKcVDSCdxKBisDN9Zu=neg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>
On Sat, Aug 23, 2014 at 2:44 AM, Ian Hickson <ian@hixie.ch> wrote:
[snip]

>    load-settings=""    A JSON-encoded dictionary to pass to the Request
>                        constructor.
>
>
I'm not a big fan of JSON attributes for this purpose, for a couple of
reasons:
* They're likely to add implementation complexity, since these instructions
must be read by the preloader, which at least for Blink & Gecko is on the
parser thread, and cannot "do" JS AFAIK. It can probably be solved with a
thread-safe JSON parser, but it'd add extra complexity.
* A non-scientific sample of authors seems to object to them, and I have to
admit that they seems weird as part of markup

What's the use-case that requires a Request constructor? Is it just for
"future friendliness"?
If so, maybe we can expose that only through JS initially, see what people
use it for, and if it makes sense add it to markup later on?
Received on Tuesday, 2 September 2014 08:34:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:30 UTC