- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 27 Mar 2014 11:56:45 -0700
- To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
- Cc: Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 27 March 2014 01:50, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com> wrote: >> A <-- B <-- D >> \- C >> I'd assume C would make progress before D given it is closer to the root. >> > > Thank you. 'Closer to the root' is a good reason. I had assumed an implementation that wouldn't respect this "closer to the root" property, but that isn't the only implementation I can imagine. Note that you haven't really said anything at all about the relative priority of C and D. It could be that a "longer" tail is actually more interesting to the client, but either way, the client has the means of expressing an actual preference using prioritization. In all other cases, the server is left to guess. > > If B is closed, then do C and D have the same precedence? > > A <-- D > \- C Same as above. C and D are assigned no relative weighting or dependency, so the order in which the server allocates resources is indeterminate.
Received on Thursday, 27 March 2014 18:57:14 UTC