W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Nit: Server-sent priority

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 18 Jun 2013 15:42:34 -0700
Message-ID: <CABkgnnUWPkqKQEfc3sm_7_nLFJVyDrvbKRVTFsUV19fRfrezzQ@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
We discussed the possibility that a server could send PRIORITY (either
in its own frame or attached to HEADERS).  The idea was that the
server could advise a client about the priority that it is applying,
which might be different to the priority that a client requested.

This adds a challenge for clients: does the client now provide updated
priorities that are relative to the priorities that it sent
previously, or relative to the priority that the server has indicated?

e.g., client sends three requests, priority 7, 10 and 15.  Server
responds and indicates priorities of 3, 5 and 7.  If the client wants
to issue a new request that is higher priority than the lowest
priority existing request, does it indicate a priority of between 10
and 15?  Or does it indicate a priority of 6?

This editor wants to know.  I think that the easiest approach would be
to stipulate that the priorities spaces are independent and that
client priorities are only relative to client priorities.
Unfortunately, that means that I need to include the example above as
well.

I don't want to prohibit servers from sending priority, because I
believe that it could be useful for a client to understand how
priority is being applied.
Received on Tuesday, 18 June 2013 22:43:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC