W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Sending priority from a server

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 11 Jul 2014 19:42:26 -0700
Message-ID: <CABkgnnWHE8LmEFbs4=qP=LTcG-hdbu3h-WtXZDaj0pKwxa2fwQ@mail.gmail.com>
To: David Krauss <potswa@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 11 July 2014 18:12, David Krauss <potswa@gmail.com> wrote:
> Prioritization isn’t a choice. Everything must be assigned a priority in a prioritizing multiplexer.
> Is it reasonable to require that every PUSH gets default priority? Certainly not; the application very probably has some idea of the relative urgency of the information. Is the HTTP/2 definition of priority strong enough to stop a server from applying priority anyway? Also no; even if the priority is nominally default a server can order frames however it likes.
> The urge to put something clever in every special case is a destructive one. At most, second-guessing should be discouraged by a note that initialized push priority is voluntary information from the server, and usually should not be taken as a basis for negotiation. But, any program that tries to treat the other side as a slave (client or server) by constructive interpretation of the protocol is going to act pathologically anyway.

I'm not sure what point you are trying to make here.  Can you turn
that into something actionable?  a) accept the PR, b) reject the PR,
c) make some other change ?
Received on Saturday, 12 July 2014 02:42:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC