- From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
- Date: Wed, 16 Jul 2014 12:20:50 +0000
- To: Martin Thomson <martin.thomson@gmail.com>, David Krauss <potswa@gmail.com>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
So I think that where we're heading to is the following: - The priority information included in a PRIORITY frame or a HEADER frame is a hint from a client to the server on how to allocate resources. - There are optional priority fields in the PUSH_PROMISE frame that allows a server to expose its intent on how it will allocate resources for pushed streams. This would suit me. I can draft an updated proposal for this. Hervé. > -----Original Message----- > From: Martin Thomson [mailto:martin.thomson@gmail.com] > Sent: mercredi 16 juillet 2014 01:30 > To: David Krauss > Cc: RUELLAN Herve; HTTP Working Group > Subject: Re: #539: Priority from server to client > > On 15 July 2014 16:21, David Krauss <potswa@gmail.com> wrote: > > > > If there’s still any confusion, to be clear: the latest proposal appears to apply > only to PUSH_PROMISE and nothing else, so that’s what I’m talking about. > > If you are talking about the same proposal (#526), then I don't think > that you claim is well supported by the content of that proposal. I > think that if that is the case, then we need to have an updated > proposal.
Received on Wednesday, 16 July 2014 12:21:39 UTC