RE: Priority straw man

From my understanding, a good download order for resources is:
- Javascript first, one resource at a time, in document order;
- CSS
- Media, possibly in parallel, as with progressive encoding, this allows early partial rendering.

This means that a specific ordering is desirable, but it may not be the document order, in particular because there are good reasons to put the Javascripts at the end of the document.

So I think that this feature is important.

Hervé.

> -----Original Message-----
> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> Sent: mardi 4 février 2014 18:37
> To: RUELLAN Herve
> Cc: Mike Bishop; HTTP Working Group
> Subject: Re: Priority straw man
> 
> On 4 February 2014 09:30, RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
> wrote:
> > However, as Mike said, it makes it hard to insert a new bucket in the middle
> of the list.
> > To go from (A, F) <- (B, C, G) <- (D, E)
> > To (A, F) <- (H) <- (B, C, G) <- (D, E), many re-prioritization are necessary.
> 
> Yes, this is true.  A more important question is whether this is a
> feature that is important enough to justify the additional complexity.

Received on Thursday, 6 February 2014 09:47:10 UTC