Re: Concerns about HTTP/2 Priority

On Thu, Nov 6, 2014 at 10:03 AM, Francesco Chemolli <kinkie@squid-cache.org>
wrote:

> > I'm still of the opinion that no significant loss of performance would
> > happen if the client just sent a single priority bit meaning:
> >
> >   '0'
> >         The fetch is happening in a background context ie:
> >           * outside of scroll-regions viewport
> >           * in covered tab
> >           * in hidden window
> >           * screen-saver is running
> >           * from a batch-job
> >
> >   '1'
> >         The fetch is happening in a foreground context ie:
> >           * in view
> >           * user is tapping his fingers
> >           * from a real-time transaction
> >
> > And I think the entire priority verbiage should be replaced by
> > something like that and any more advanced priority communications/state
> > relegated to extensions.
>
> It's a bit extreme, but it's the kind of simplicity that pays the
> biggest returns on implementation complexity.
> I like this; can we discuss the idea a bit, and maybe straw-hat it?


Browsers need far more than a single bit. The dependency model is based on
direct feedback (and development experience) from a number of large,
existing apps, at Google and beyond -- no they're not unique, todays "large
apps" are tomorrow's everyday apps.

ig